DBMS > Ehcache vs. H2 vs. IBM Cloudant vs. PlanetScale vs. RocksDB

System Properties Comparison Ehcache vs. H2 vs. IBM Cloudant vs. PlanetScale vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Database as a Service offering based on Apache CouchDB

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

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

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

Website

www.ehcache.org

www.h2database.com

www.ibm.com/products/cloudant

planetscale.com

rocksdb.org

Technical documentation

www.ehcache.org/documentation

www.h2database.com/html/main.html

cloud.ibm.com/docs/Cloudant

planetscale.com/docs

github.com/facebook/rocksdb/wiki

Developer

Terracotta Inc, owned by Software AG

Thomas Mueller

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

PlanetScale

Facebook, Inc.

Initial release

2009

2005

2010

2020

2013

Current release

3.10.0, March 2022

2.2.220, July 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

dual-licence (Mozilla public license, Eclipse public license)

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

Erlang

C++

Server operating systems

All OS with a Java VM

hosted

Docker
Linux
macOS

Linux

Data scheme

schema-free

yes

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

JCache

JDBC
ODBC

RESTful HTTP/JSON API

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

Supported programming languages

Java

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Java Stored Procedures and User-Defined Functions

View functions (Map-Reduce) in JavaScript

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

With clustering: 2 database servers on different computers operate on identical copies of a database

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

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual 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

yes

supports JTA and can work as an XA resource

ACID

atomic operations within a document possible

ACID at shard level

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Optimistic locking

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

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.