DBMS > Datomic vs. Dgraph vs. RDF4J vs. RocksDB

System Properties Comparison Datomic vs. Dgraph vs. RDF4J vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Distributed and scalable native Graph DBMS

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)

Primary database model

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

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	0.71
Rank	#231	Overall
	#9	RDF stores

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

Website

Technical documentation

docs.datomic.com

dgraph.io/docs

rdf4j.org/documentation

github.com/facebook/rocksdb/wiki

Developer

Cognitect

Dgraph Labs, Inc.

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

Facebook, Inc.

Initial release

2012

2016

2004

2013

Current release

1.0.6735, June 2023

8.11.4, April 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

BSD

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, Clojure

Java

C++

Server operating systems

All OS with a Java VM

Linux
OS X
Windows

Linux
OS X
Unix
Windows

Linux

Data scheme

yes

schema-free

yes

RDF Schemas

schema-free

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

APIs and other access methods

RESTful HTTP API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

C++ API
Java API

Supported programming languages

Clojure
Java

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

yes

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Synchronous replication via Raft

none

yes

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

Transaction concepts

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

ACID

Isolation support depends on the API used

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

in-memory storage is supported as well

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Planned for future releases

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.