DBMS > EJDB vs. Fauna vs. RocksDB vs. TerarkDB vs. TimescaleDB

System Properties Comparison EJDB vs. Fauna vs. RocksDB vs. TerarkDB vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Fauna provides a web-native interface, with support for GraphQL and custom business logic that integrates seamlessly with the rest of the serverless ecosystem. The underlying globally distributed storage and compute platform is fast, consistent, and reliable, with a modern security infrastructure.

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Document store

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Key-value store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1.55
Rank	#151	Overall
	#26	Document stores
	#14	Graph DBMS
	#71	Relational DBMS
	#13	Time Series DBMS

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

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

github.com/Softmotions/ejdb

fauna.com

rocksdb.org

github.com/bytedance/terarkdb

www.timescale.com

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

docs.fauna.com

github.com/facebook/rocksdb/wiki

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.timescale.com

Developer

Softmotions

Fauna, Inc.

Facebook, Inc.

ByteDance, originally Terark

Timescale

Initial release

2012

2014

2013

2016

2017

Current release

9.2.1, May 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

BSD

commercial

restricted open source version available

Open Source

Apache 2.0

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

Scala

C++

Server operating systems

server-less

hosted

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

full PostgreSQL SQL syntax

APIs and other access methods

in-process shared library

RESTful HTTP API

C++ API
Java API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C#
Go
Java
JavaScript
Python
Ruby
Scala
Swift

C
C++
Go
Java
Perl
Python
Ruby

C++
Java

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

consistent hashing

horizontal partitioning

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

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

Identity management, authentication, and access control

fine grained access rights according to SQL-standard

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.