DBMS > Google BigQuery vs. HugeGraph vs. Prometheus vs. Splice Machine

System Properties Comparison Google BigQuery vs. HugeGraph vs. Prometheus vs. Splice Machine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A fast-speed and highly-scalable Graph DBMS

Open-source Time Series DBMS and monitoring system

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

Primary database model

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

cloud.google.com/bigquery

github.com/hugegraph
hugegraph.apache.org

prometheus.io

splicemachine.com

Technical documentation

cloud.google.com/bigquery/docs

hugegraph.apache.org/docs

prometheus.io/docs

splicemachine.com/how-it-works

Developer

Google

Baidu

Splice Machine

Initial release

2010

2018

2015

2014

Current release

0.9

3.1, March 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

AGPL 3.0, commercial license available

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

Java

Server operating systems

hosted

Linux
macOS
Unix

Linux
Windows

Linux
OS X
Solaris
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

also supports composite index and range index

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

Java API
RESTful HTTP API
TinkerPop Gremlin

RESTful HTTP/JSON API

JDBC
Native Spark Datasource
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Groovy
Java
Python

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

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

asynchronous Gremlin script jobs

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

depending on used storage backend, e.g. Cassandra and HBase

Sharding

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

by Federation

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

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

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)

Users, roles and permissions

Access rights for users, groups and roles 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.