DBMS > RocksDB vs. Tarantool vs. Tkrzw vs. VoltDB

System Properties Comparison RocksDB vs. Tarantool vs. Tkrzw vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Key-value store

Document store
Key-value store
Relational DBMS

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

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

Technical documentation

github.com/facebook/rocksdb/wiki

www.tarantool.io/en/doc

docs.voltdb.com

Developer

Facebook, Inc.

Mikio Hirabayashi

VoltDB Inc.

Initial release

2013

2008

2020

2010

Current release

9.2.1, May 2024

2.10.0, May 2022

0.9.3, August 2020

11.3, April 2022

License

Commercial or Open Source

Open Source

BSD

Open Source

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

Open Source

Apache Version 2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C++

Java, C++

Server operating systems

Linux

BSD
Linux
macOS

Linux
macOS

Linux
OS X

for development

Data scheme

schema-free

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

schema-free

yes

Typing

predefined data types such as float or date

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

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

Full-featured ANSI SQL support

yes

only a subset of SQL 99

APIs and other access methods

C++ API
Java API

Open binary protocol

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

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

C++
Java
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Lua, C and SQL stored procedures

Java

Triggers

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

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

yes

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

Snapshots and command 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

yes

using specific database classes

User concepts

Access control

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

Users and roles with access to stored procedures

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.