DBMS > Graph Engine vs. RDF4J vs. RocksDB vs. TimescaleDB vs. VoltDB

System Properties Comparison Graph Engine vs. RDF4J vs. RocksDB vs. TimescaleDB vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

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

Graph DBMS
Key-value store

Secondary database models

Relational DBMS

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

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

Technical documentation

www.graphengine.io/docs/manual

rdf4j.org/documentation

github.com/facebook/rocksdb/wiki

docs.timescale.com

docs.voltdb.com

Developer

Microsoft

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Facebook, Inc.

Timescale

VoltDB Inc.

Initial release

2010

2004

2013

2017

2010

Current release

9.2.1, May 2024

2.15.0, May 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

BSD

Open Source

Apache 2.0

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

.NET and C

Java

C++

Java, C++

Server operating systems

.NET

Linux
OS X
Unix
Windows

Linux

Linux
OS X
Windows

Linux
OS X

for development

Data scheme

yes

RDF Schemas

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

full PostgreSQL SQL syntax

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

C++ API
Java API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C#
C++
F#
Visual Basic

Java
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

horizontal partitioning

yes, across time and space (hash partitioning) attributes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication with hot standby and reads on replicas

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

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Isolation support depends on the API used

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

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 storage is supported as well

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

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.