DBMS > RocksDB vs. Tarantool vs. TigerGraph vs. ToroDB

System Properties Comparison RocksDB vs. Tarantool vs. TigerGraph vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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 complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Key-value store

Document store
Key-value store
Relational DBMS

Graph DBMS

Document store

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

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

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

rocksdb.org

www.tarantool.io

www.tigergraph.com

github.com/torodb/server

Technical documentation

github.com/facebook/rocksdb/wiki

www.tarantool.io/en/doc

docs.tigergraph.com

Developer

Facebook, Inc.

8Kdata

Initial release

2013

2008

2017

2016

Current release

9.2.1, May 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

BSD

Open Source

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

commercial

Open Source

AGPL-V3

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

Server operating systems

Linux

BSD
Linux
macOS

Linux

All OS with a Java 7 VM

Data scheme

schema-free

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

yes

schema-free

Typing

predefined data types such as float or date

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

yes

string, integer, double, boolean, date, object_id

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

SQL-like query language (GSQL)

APIs and other access methods

C++ API
Java API

Open binary protocol

GSQL (TigerGraph Query Language)
Kafka
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

Server-side scripts

Stored procedures

Lua, C and SQL stored procedures

yes

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.

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)

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

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

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

Role-based access control

Access rights for 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.