DBMS > Dragonfly vs. Oracle NoSQL vs. RocksDB vs. TerarkDB vs. Yaacomo

System Properties Comparison Dragonfly vs. Oracle NoSQL vs. RocksDB vs. TerarkDB vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

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)

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Key-value store

Document store
Key-value store
Relational DBMS

Key-value store

Relational DBMS

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

Score	0.49
Rank	#261	Overall
	#38	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

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

Website

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

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

rocksdb.org

github.com/bytedance/terarkdb

yaacomo.com

Technical documentation

www.dragonflydb.io/docs

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

github.com/facebook/rocksdb/wiki

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

DragonflyDB team and community contributors

Oracle

Facebook, Inc.

ByteDance, originally Terark

Q2WEB GmbH

Initial release

2023

2011

2013

2016

2009

Current release

1.0, March 2023

24.1, May 2024

9.2.1, May 2024

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

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

Open Source

BSD

commercial

restricted open source version available

commercial

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++

Server operating systems

Linux

Linux
Solaris SPARC/x86

Linux

Android
Linux
Windows

Data scheme

scheme-free

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

schema-free

yes

Typing

predefined data types such as float or date

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

optional

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

SQL-like DML and DDL statements

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

RESTful HTTP API

C++ API
Java API

JDBC
ODBC

Supported programming languages

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
JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

Lua

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

yes

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

configurable

ACID within a storage node (=shard)

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

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

off heap cache

yes

User concepts

Access control

Password-based authentication

Access rights for users and roles

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.