DBMS > Dragonfly vs. GBase vs. RocksDB vs. Tarantool

System Properties Comparison Dragonfly vs. GBase vs. RocksDB vs. Tarantool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Key-value store

Relational DBMS

Key-value store

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

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

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

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

www.gbase.cn

rocksdb.org

www.tarantool.io

Technical documentation

www.dragonflydb.io/docs

github.com/facebook/rocksdb/wiki

www.tarantool.io/en/doc

Developer

DragonflyDB team and community contributors

General Data Technology Co., Ltd.

Facebook, Inc.

Initial release

2023

2004

2013

2008

Current release

1.0, March 2023

GBase 8a, GBase 8s, GBase 8c

9.2.1, May 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

Open Source

BSD

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C, Java, Python

C++

C and C++

Server operating systems

Linux

BSD
Linux
macOS

Data scheme

scheme-free

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

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

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Standard with numerous extensions

Full-featured ANSI SQL support

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
C API
JDBC
ODBC

C++ API
Java API

Open binary protocol

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
Perl
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

Lua

user defined functions

Lua, C and SQL stored procedures

Triggers

publish/subscribe channels provide some trigger functionality

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

horizontal partitioning

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

ACID

yes

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Password-based authentication

yes

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.