DBMS > Ehcache vs. Faircom DB vs. Google Cloud Spanner vs. Machbase Neo vs. RocksDB

System Properties Comparison Ehcache vs. Faircom DB vs. Google Cloud Spanner vs. Machbase Neo vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Key-value store

Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

Key-value store

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	2.89
Rank	#103	Overall
	#52	Relational DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

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

Website

www.ehcache.org

www.faircom.com/products/faircom-db

cloud.google.com/spanner

machbase.com

rocksdb.org

Technical documentation

www.ehcache.org/documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

cloud.google.com/spanner/docs

machbase.com/dbms

github.com/facebook/rocksdb/wiki

Developer

Terracotta Inc, owned by Software AG

FairCom Corporation

Google

Machbase

Facebook, Inc.

Initial release

2009

1979

2017

2013

Current release

3.10.0, March 2022

V12, November 2020

V8.0, August 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Restricted, free version available

commercial

free test version available

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

ANSI C, C++

C++

Server operating systems

All OS with a Java VM

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

hosted

Linux
macOS
Windows

Linux

Data scheme

schema-free

schema free, schema optional, schema required, partial schema,

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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, ANSI SQL with proprietary extensions

yes

Query statements complying to ANSI 2011

SQL-like query language

APIs and other access methods

JCache

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

C++ API
Java API

Supported programming languages

Java

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Multi-source replication with 3 replicas for regional instances.

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

yes

supports JTA and can work as an XA resource

tunable from ACID to Eventually Consistent

ACID

Strict serializable isolation

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

Yes, tunable from durable to delayed durability to in-memory

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

volatile and lookup table

yes

User concepts

Access control

Fine grained access rights according to SQL-standard with additional protections for files

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

simple password-based access control

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.