DBMS > Apache Drill vs. CockroachDB vs. Datomic vs. EsgynDB vs. RocksDB

System Properties Comparison Apache Drill vs. CockroachDB vs. Datomic vs. EsgynDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	6.10
Rank	#58	Overall
	#33	Relational DBMS

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

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

Website

drill.apache.org

www.cockroachlabs.com

www.datomic.com

www.esgyn.cn

rocksdb.org

Technical documentation

drill.apache.org/docs

www.cockroachlabs.com/docs

docs.datomic.com

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Cockroach Labs

Cognitect

Esgyn

Facebook, Inc.

Initial release

2012

2015

2012

2015

2013

Current release

1.20.3, January 2023

23.1.1, May 2023

1.0.6735, June 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0, commercial license available

commercial

limited edition free

commercial

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

C++, Java

C++

Server operating systems

Linux
OS X
Windows

Linux
macOS
Windows

All OS with a Java VM

Linux

Data scheme

schema-free

dynamic schema

yes

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

SQL SELECT statement is SQL:2003 compliant

yes, wire compatible with PostgreSQL

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

RESTful HTTP API

ADO.NET
JDBC
ODBC

C++ API
Java API

Supported programming languages

C++

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

Clojure
Java

All languages supporting JDBC/ODBC/ADO.Net

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Transaction Functions

Java Stored Procedures

Triggers

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

none

But extensive use of caching in the application peers

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

none

But extensive use of caching in the application peers

Multi-source replication between multi datacenters

yes

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

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

Role-based access control

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.