DBMS > Apache Drill vs. Datomic vs. Dgraph vs. RocksDB vs. RRDtool

System Properties Comparison Apache Drill vs. Datomic vs. Dgraph vs. RocksDB vs. RRDtool

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Distributed and scalable native Graph DBMS

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

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Document store
Relational DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

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

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Website

oss.oetiker.ch/rrdtool

Technical documentation

drill.apache.org/docs

docs.datomic.com

dgraph.io/docs

github.com/facebook/rocksdb/wiki

oss.oetiker.ch/rrdtool/doc

Developer

Apache Software Foundation

Cognitect

Dgraph Labs, Inc.

Facebook, Inc.

Tobias Oetiker

Initial release

2012

2016

2013

1999

Current release

1.20.3, January 2023

1.0.6735, June 2023

9.2.1, May 2024

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

limited edition free

Open Source

Apache 2.0

Open Source

BSD

Open Source

GPL V2 and FLOSS

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

C++

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux
OS X
Windows

Linux

HP-UX
Linux

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

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

C++ API
Java API

in-process shared library
Pipes

Supported programming languages

C++

Clojure
Java

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

C
C++
Go
Java
Perl
Python
Ruby

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Transaction Functions

Triggers

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

yes

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Synchronous replication via Raft

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

none

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

Durability

Support for making data persistent

Depending on the underlying data source

yes

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

yes

In-memory capabilities

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

Depending on the underlying data source

yes

recommended only for testing and development

yes

User concepts

Access control

Depending on the underlying data source

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.