DBMS > Graph Engine vs. RethinkDB vs. RocksDB vs. ToroDB

System Properties Comparison Graph Engine vs. RethinkDB vs. RocksDB 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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

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

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

Primary database model

Graph DBMS
Key-value store

Document store

Key-value store

Document store

Secondary database models

Spatial DBMS

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

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	2.84
Rank	#106	Overall
	#19	Document stores

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

www.graphengine.io

rethinkdb.com

rocksdb.org

github.com/torodb/server

Technical documentation

www.graphengine.io/docs/manual

rethinkdb.com/docs

github.com/facebook/rocksdb/wiki

Developer

Microsoft

The Linux Foundation

since July 2017

Facebook, Inc.

8Kdata

Initial release

2010

2009

2013

2016

Current release

2.4.1, August 2020

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2

Open Source

BSD

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

.NET and C

C++

Java

Server operating systems

.NET

Linux
OS X
Windows

Linux

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

APIs and other access methods

RESTful HTTP API

C++ API
Java API

Supported programming languages

C#
C++
F#
Visual Basic

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

range based

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic single-document operations

yes

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

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

yes

User concepts

Access control

yes

users and table-level permissions

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.