DBMS > BigchainDB vs. Google BigQuery vs. IBM Db2 warehouse vs. VoltDB

System Properties Comparison BigchainDB vs. Google BigQuery vs. IBM Db2 warehouse vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Large scale data warehouse service with append-only tables

Cloud-based data warehousing service

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

Document store

Relational DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.bigchaindb.com

cloud.google.com/bigquery

www.ibm.com/products/db2/warehouse

www.voltdb.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

cloud.google.com/bigquery/docs

docs.voltdb.com

Developer

Google

IBM

VoltDB Inc.

Initial release

2016

2010

2014

2010

Current release

11.3, April 2022

License

Commercial or Open Source

Open Source

AGPL v3

commercial

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

Python

Java, C++

Server operating systems

Linux

hosted

Linux
OS X

for development

Data scheme

schema-free

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.

Import/export of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

CLI Client
RESTful HTTP API

RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
OLE DB

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

PL/SQL, SQL PL

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

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,with MongoDB ord RethinkDB

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

yes

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 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.