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

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

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

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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

Primary database model

Key-value store
Wide column store

Key-value store

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

cloud.google.com/bigtable

www.oracle.com/java/coherence

planetscale.com

rocksdb.org

Technical documentation

cloud.google.com/bigtable/docs

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

planetscale.com/docs

github.com/facebook/rocksdb/wiki

Developer

Google

Oracle

PlanetScale

Facebook, Inc.

Initial release

2015

2007

2020

2013

Current release

14.1, August 2023

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

BSD

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

Server operating systems

hosted

All OS with a Java VM

Docker
Linux
macOS

Linux

Data scheme

schema-free

yes

schema-free

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

with proprietary extensions

APIs and other access methods

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

JCache
JPA
RESTful HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

Supported programming languages

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

.Net
C++
Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Live Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

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

Multi-source replication
Source-replica replication

yes

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-row operations

configurable

ACID at shard level

yes

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

optionally

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 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 with fine-grained authorization concept

no user groups or roles

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.