DBMS > Drizzle vs. FoundationDB vs. Lovefield vs. RocksDB

System Properties Comparison Drizzle vs. FoundationDB vs. Lovefield vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

Embeddable relational database for web apps written in pure JavaScript

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

Primary database model

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Key-value store

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.33
Rank	#286	Overall
	#131	Relational DBMS

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

Website

github.com/apple/foundationdb

google.github.io/lovefield

rocksdb.org

Technical documentation

apple.github.io/foundationdb

github.com/google/lovefield/blob/master/docs/spec_index.md

github.com/facebook/rocksdb/wiki

Developer

Drizzle project, originally started by Brian Aker

FoundationDB

Google

Facebook, Inc.

Initial release

2008

2013

2014

2013

Current release

7.2.4, September 2012

6.2.28, November 2020

2.1.12, February 2017

9.2.1, May 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache 2.0

Open Source

Apache 2.0

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

C++

JavaScript

C++

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux

Data scheme

yes

schema-free

some layers support schemas

yes

schema-free

Typing

predefined data types such as float or date

yes

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

SQL

Support of SQL

yes

with proprietary extensions

supported in specific SQL layer only

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

JDBC

C++ API
Java API

Supported programming languages

C
C++
Java
PHP

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

in SQL-layer only

Triggers

hooks for callbacks inside the server can be used.

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Foreign keys

Referential integrity

yes

in SQL-layer only

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.