DBMS > RocksDB vs. TerminusDB vs. TypeDB vs. VoltDB

System Properties Comparison RocksDB vs. TerminusDB vs. TypeDB 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)

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

TypeDB is a strongly-typed database with a rich and logical type system and TypeQL as its query language

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

Graph DBMS

Graph DBMS
Relational DBMS

Often described as a 'hyper-relational' database, since it implements the 'Entity-Relationship Paradigm' to manage complex data structures and ontologies.

Relational DBMS

Secondary database models

Document store
RDF store

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

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

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.65
Rank	#234	Overall
	#20	Graph DBMS
	#107	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

Technical documentation

github.com/facebook/rocksdb/wiki

terminusdb.github.io/terminusdb/#

typedb.com/docs

docs.voltdb.com

Developer

Facebook, Inc.

DataChemist Ltd.

Vaticle

VoltDB Inc.

Initial release

2013

2018

2016

2010

Current release

8.11.4, April 2024

11.0.0, January 2023

2.26.3, January 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

BSD

Open Source

GPL V3

Open Source

GPL Version 3, commercial licenses available

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

Prolog, Rust

Java

Java, C++

Server operating systems

Linux

Linux
OS X
Windows

Linux
OS X

for development

Data scheme

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (WOQL)

yes

only a subset of SQL 99

APIs and other access methods

C++ API
Java API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

gRPC protocol
TypeDB Console (shell)
TypeDB Studio (Visualisation software- previously TypeDB Workbase)

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

JavaScript
Python

All JVM based languages
Groovy
Java
JavaScript (Node.js)
Python
Scala

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Graph Partitioning

Sharding

by using Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Journaling Streams

Multi-source replication

by using Cassandra

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

by using Apache Kafka and Apache Zookeeper

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

substituted by the relationship feature

FOREIGN KEY constraints are not supported

Transaction concepts

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

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

in-memory journaling

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

User concepts

Access control

Role-based access control

yes

at REST API level; other APIs in progress

Users and roles with access to stored procedures

More information provided by the system vendor

Specific characteristics

TypeDB is a polymorphic database with a conceptual data model, a strong subtyping...
» more

Competitive advantages

TypeDB provides a new level of expressivity, extensibility, interoperability, and...
» more

Typical application scenarios

Life sciences : TypeDB makes working with biological data much easier and accelerates...
» more

Licensing and pricing models

Apache f or language drivers, and AGPL and Commercial for the database server. The...
» more

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.