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

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

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

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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

Primary database model

Document store
Relational DBMS

Secondary database models

Document store
Spatial 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	1.59
Rank	#151	Overall
	#70	Relational DBMS

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

Website

Technical documentation

drill.apache.org/docs

docs.datomic.com

dgraph.io/docs

planetscale.com/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Cognitect

Dgraph Labs, Inc.

PlanetScale

Facebook, Inc.

Initial release

2012

2016

2020

2013

Current release

1.20.3, January 2023

1.0.6735, June 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

limited edition free

Open Source

Apache 2.0

commercial

Open Source

BSD

Cloud-based only

Only available as a cloud service

yes

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
OS X
Windows

Docker
Linux
macOS

Linux

Data scheme

schema-free

yes

schema-free

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

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

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

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

Supported programming languages

C++

Clojure
Java

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Transaction Functions

yes

proprietary syntax

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

yes

Sharding

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

Multi-source replication
Source-replica replication

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

yes

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Planned for future releases

Users with fine-grained authorization concept

no user groups or 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.