DBMS > Google BigQuery vs. HEAVY.AI vs. HugeGraph vs. VoltDB

System Properties Comparison Google BigQuery vs. HEAVY.AI vs. HugeGraph vs. VoltDB

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 high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

A fast-speed and highly-scalable Graph DBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

cloud.google.com/bigquery

github.com/heavyai/heavydb
www.heavy.ai

github.com/hugegraph
hugegraph.apache.org

www.voltdb.com

Technical documentation

cloud.google.com/bigquery/docs

docs.heavy.ai

hugegraph.apache.org/docs

docs.voltdb.com

Developer

Google

HEAVY.AI, Inc.

Baidu

VoltDB Inc.

Initial release

2010

2016

2018

2010

Current release

5.10, January 2022

0.9

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache Version 2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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++ and CUDA

Java

Java, C++

Server operating systems

hosted

Linux

Linux
macOS
Unix

Linux
OS X

for development

Data scheme

yes

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

also supports composite index and range index

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

Java API
RESTful HTTP API
TinkerPop Gremlin

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

Groovy
Java
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

asynchronous Gremlin script jobs

Java

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

yes

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

edges in graph

FOREIGN KEY constraints are not supported

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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)

fine grained access rights according to SQL-standard

Users, roles and permissions

Users and roles with access to stored procedures

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.