DBMS > Apache Drill vs. Datomic vs. RocksDB vs. TimescaleDB

System Properties Comparison Apache Drill vs. Datomic vs. RocksDB vs. TimescaleDB

Please select another system to include it in the comparison.

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

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

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

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

Technical documentation

drill.apache.org/docs

docs.datomic.com

github.com/facebook/rocksdb/wiki

docs.timescale.com

Developer

Apache Software Foundation

Cognitect

Facebook, Inc.

Timescale

Initial release

2012

2013

2017

Current release

1.20.3, January 2023

1.0.7075, December 2023

9.2.1, May 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

limited edition free

Open Source

BSD

Open Source

Apache 2.0

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

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

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

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

SQL SELECT statement is SQL:2003 compliant

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

C++ API
Java API

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

Supported programming languages

C++

Clojure
Java

C
C++
Go
Java
Perl
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

Transaction Functions

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

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

horizontal partitioning

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

yes

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

fine grained access rights according to SQL-standard

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.