DBMS > Cachelot.io vs. Datomic vs. Dragonfly vs. RocksDB vs. TerarkDB

System Properties Comparison Cachelot.io vs. Datomic vs. Dragonfly vs. RocksDB vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

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

Primary database model

Key-value store

Relational DBMS

Key-value store

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.41
Rank	#266	Overall
	#38	Key-value stores

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

cachelot.io

www.datomic.com

github.com/dragonflydb/dragonfly
www.dragonflydb.io

rocksdb.org

github.com/bytedance/terarkdb

Technical documentation

docs.datomic.com

www.dragonflydb.io/docs

github.com/facebook/rocksdb/wiki

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Cognitect

DragonflyDB team and community contributors

Facebook, Inc.

ByteDance, originally Terark

Initial release

2015

2012

2023

2013

2016

Current release

1.0.6735, June 2023

1.0, March 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Simplified BSD License

commercial

limited edition free

Open Source

BSL 1.1

Open Source

BSD

commercial

restricted open source version available

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, Clojure

C++

Server operating systems

FreeBSD
Linux
OS X

All OS with a Java VM

Linux

Data scheme

schema-free

yes

scheme-free

schema-free

Typing

predefined data types such as float or date

yes

strings, hashes, lists, sets, sorted sets, bit arrays

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

APIs and other access methods

Memcached protocol

RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protocol

C++ API
Java API

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

Clojure
Java

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

C
C++
Go
Java
Perl
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

yes

Transaction Functions

Lua

Triggers

By using transaction functions

publish/subscribe channels provide some trigger functionality

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Password-based authentication

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.