DBMS > Ehcache vs. FatDB vs. Oracle NoSQL vs. RocksDB

System Properties Comparison Ehcache vs. FatDB vs. Oracle NoSQL vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A widely adopted Java cache with tiered storage options

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

Primary database model

Key-value store

Document store
Key-value store

Document store
Key-value store
Relational DBMS

Key-value store

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

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

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

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

Website

www.ehcache.org

www.oracle.com/database/nosql/technologies/nosql

rocksdb.org

Technical documentation

www.ehcache.org/documentation

docs.oracle.com/en/database/other-databases/nosql-database/index.html

github.com/facebook/rocksdb/wiki

Developer

Terracotta Inc, owned by Software AG

FatCloud

Oracle

Facebook, Inc.

Initial release

2009

2012

2011

2013

Current release

3.10.0, March 2022

24.1, May 2024

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

BSD

Cloud-based only

Only available as a cloud service

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

All OS with a Java VM

Windows

Linux
Solaris SPARC/x86

Linux

Data scheme

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

Typing

predefined data types such as float or date

yes

optional

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

Via inetgration in SQL Server

SQL-like DML and DDL statements

APIs and other access methods

JCache

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP API

C++ API
Java API

Supported programming languages

Java

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

Cache Event Listeners

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

selectable replication factor

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

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

configurable

ACID within a storage node (=shard)

yes

Concurrency

Support for concurrent manipulation of data

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

off heap cache

yes

User concepts

Access control

Can implement custom security layer via applications

Access rights for users and 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.