DBMS > FoundationDB vs. Heroic vs. Oracle Coherence vs. RocksDB vs. Warp 10

System Properties Comparison FoundationDB vs. Heroic vs. Oracle Coherence vs. RocksDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Description

Ordered key-value store. Core features are complimented by layers.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Oracles in-memory data grid solution

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Time Series DBMS

Key-value store

Time Series DBMS

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

Score	1.06
Rank	#185	Overall
	#31	Document stores
	#28	Key-value stores
	#85	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

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

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

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

github.com/apple/foundationdb

github.com/spotify/heroic

www.oracle.com/java/coherence

rocksdb.org

www.warp10.io

Technical documentation

apple.github.io/foundationdb

spotify.github.io/heroic

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

github.com/facebook/rocksdb/wiki

www.warp10.io/content/02_Getting_started

Developer

FoundationDB

Spotify

Oracle

Facebook, Inc.

SenX

Initial release

2013

2014

2007

2013

2015

Current release

6.2.28, November 2020

14.1, August 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

Open Source

BSD

Open Source

Apache License 2.0

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

C++

Java

C++

Java

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux

Linux
OS X
Windows

Data scheme

schema-free

some layers support schemas

schema-free

Typing

predefined data types such as float or date

some layers support typing

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

via Elasticsearch

SQL

Support of SQL

supported in specific SQL layer only

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

JCache
JPA
RESTful HTTP API

C++ API
Java API

HTTP API
Jupyter
WebSocket

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
C++
Java

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

in SQL-layer only

yes

WarpScript

Triggers

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, with selectable consistency level

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

in SQL-layer only

Transaction concepts

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

ACID

configurable

yes

Concurrency

Support for concurrent manipulation of data

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

authentification to access the cache via certificates or http basic authentication

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.