DBMS > Google BigQuery vs. Prometheus vs. Sphinx vs. Splice Machine vs. Valentina Server

System Properties Comparison Google BigQuery vs. Prometheus vs. Sphinx vs. Splice Machine vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Open-source Time Series DBMS and monitoring system

Open source search engine for searching in data from different sources, e.g. relational databases

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Object-relational database and reports server

Primary database model

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

cloud.google.com/bigquery

Technical documentation

cloud.google.com/bigquery/docs

prometheus.io/docs

sphinxsearch.com/docs

splicemachine.com/how-it-works

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Google

Sphinx Technologies Inc.

Splice Machine

Paradigma Software

Initial release

2010

2015

2001

2014

1999

Current release

3.5.1, February 2023

3.1, March 2021

5.7.5

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL version 2, commercial licence available

Open Source

AGPL 3.0, commercial license available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

Server operating systems

hosted

Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Import of XML data possible

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

yes

APIs and other access methods

RESTful HTTP/JSON API

Proprietary protocol

JDBC
Native Spark Datasource
ODBC

ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Java

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by Federation

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users, groups and roles according to SQL-standard

fine grained access rights according to SQL-standard

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.