DBMS > RocksDB vs. Stardog vs. TerminusDB vs. Vitess

System Properties Comparison RocksDB vs. Stardog vs. TerminusDB vs. Vitess

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)

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
RDF store

Document store
Spatial DBMS

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

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

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

Technical documentation

github.com/facebook/rocksdb/wiki

docs.stardog.com

terminusdb.github.io/terminusdb/#

vitess.io/docs

Developer

Facebook, Inc.

Stardog-Union

DataChemist Ltd.

The Linux Foundation, PlanetScale

Initial release

2013

2010

2018

2013

Current release

8.11.4, April 2024

7.3.0, May 2020

11.0.0, January 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

BSD

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

Open Source

GPL V3

Open Source

Apache Version 2.0, commercial licenses available

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

Java

Prolog, Rust

Server operating systems

Linux

Linux
macOS
Windows

Linux

Docker
Linux
macOS

Data scheme

schema-free

schema-free and OWL/RDFS-schema support

yes

Typing

predefined data types such as float or date

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.

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

yes

SQL

Support of SQL

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

SQL-like query language (WOQL)

yes

with proprietary extensions

APIs and other access methods

C++ API
Java API

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

JavaScript
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions and aggregates, HTTP Server extensions in Java

yes

proprietary syntax

Triggers

yes

via event handlers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication in HA-Cluster

Journaling Streams

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

Immediate Consistency in HA-Cluster

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

in-memory journaling

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

Access rights for users and roles

Role-based access control

Users with fine-grained authorization concept

no user groups or 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.