DBMS > Google Cloud Bigtable vs. Oracle Coherence vs. RocksDB vs. VoltDB

System Properties Comparison Google Cloud Bigtable vs. Oracle Coherence vs. RocksDB vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Oracles in-memory data grid solution

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

Key-value store
Wide column store

Key-value store

Relational DBMS

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

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

cloud.google.com/bigtable

www.oracle.com/java/coherence

rocksdb.org

www.voltdb.com

Technical documentation

cloud.google.com/bigtable/docs

docs.oracle.com/en/middleware/standalone/coherence

github.com/facebook/rocksdb/wiki

docs.voltdb.com

Developer

Google

Oracle

Facebook, Inc.

VoltDB Inc.

Initial release

2015

2007

2013

2010

Current release

14.1, August 2023

8.11.4, April 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

BSD

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

Java

C++

Java, C++

Server operating systems

hosted

All OS with a Java VM

Linux

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.

Secondary indexes

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JCache
JPA
RESTful HTTP API

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

.Net
C++
Java

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Java

Triggers

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

yes, with selectable consistency level

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

Atomic single-row operations

configurable

yes

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

optionally

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 rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

authentification to access the cache via certificates or http basic authentication

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.