DBMS > OrientDB vs. RocksDB vs. Tarantool vs. XTDB

System Properties Comparison OrientDB vs. RocksDB vs. Tarantool vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model DBMS (Document, Graph, Key/Value)

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 general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Graph DBMS
Key-value store

Key-value store

Document store
Key-value store
Relational 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.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

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	0.11
Rank	#343	Overall
	#46	Document stores

Website

orientdb.org

rocksdb.org

www.tarantool.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

www.orientdb.com/docs/last/index.html

github.com/facebook/rocksdb/wiki

www.tarantool.io/en/doc

www.xtdb.com/docs

Developer

OrientDB LTD; CallidusCloud; SAP

Facebook, Inc.

Juxt Ltd.

Initial release

2010

2013

2008

2019

Current release

3.2.29, March 2024

9.2.1, May 2024

2.10.0, May 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

BSD

Open Source

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

Open Source

MIT License

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

Java

C++

C and C++

Clojure

Server operating systems

All OS with a Java JDK (>= JDK 6)

Linux

BSD
Linux
macOS

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

schema-free

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

schema-free

Typing

predefined data types such as float or date

yes

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

yes, extensible-data-notation format

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 query language, no joins

Full-featured ANSI SQL support

limited SQL, making use of Apache Calcite

APIs and other access methods

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

C++ API
Java API

Open binary protocol

HTTP REST
JDBC

Supported programming languages

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

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

Clojure
Java

Server-side scripts

Stored procedures

Java, Javascript

Lua, C and SQL stored procedures

Triggers

Hooks

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

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

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

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

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

ACID

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, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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 rights for users and roles; record level security configurable

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.