DBMS > RDF4J vs. RocksDB vs. SwayDB vs. Tarantool vs. XTDB

System Properties Comparison RDF4J vs. RocksDB vs. SwayDB vs. Tarantool vs. XTDB

Editorial information provided by DB-Engines

Name

Description

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)

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

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

RDF 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	0.69
Rank	#230	Overall
	#9	RDF stores

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

Score	0.00
Rank	#382	Overall
	#59	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

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

Technical documentation

rdf4j.org/documentation

github.com/facebook/rocksdb/wiki

www.tarantool.io/en/doc

www.xtdb.com/docs

Developer

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

Facebook, Inc.

Simer Plaha

Juxt Ltd.

Initial release

2004

2013

2018

2008

2019

Current release

8.11.4, April 2024

2.10.0, May 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

BSD

Open Source

GNU Affero GPL V3.0

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

Scala

C and C++

Clojure

Server operating systems

Linux
OS X
Unix
Windows

Linux

BSD
Linux
macOS

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

Data scheme

yes

RDF Schemas

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

Full-featured ANSI SQL support

limited SQL, making use of Apache Calcite

APIs and other access methods

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

C++ API
Java API

Open binary protocol

HTTP REST
JDBC

Supported programming languages

Java
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

Java
Kotlin
Scala

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

Clojure
Java

Server-side scripts

Stored procedures

yes

Lua, C and SQL stored procedures

Triggers

yes

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

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

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

none

yes

none

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Transaction concepts

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

ACID

Isolation support depends on the API used

yes

Atomic execution of operations

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

in-memory storage is supported as well

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