DBMS > Apache Druid vs. EJDB vs. PlanetScale vs. RocksDB

System Properties Comparison Apache Druid vs. EJDB vs. PlanetScale vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Relational DBMS
Time Series DBMS

Document store

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

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

Website

druid.apache.org

github.com/Softmotions/ejdb

planetscale.com

rocksdb.org

Technical documentation

druid.apache.org/docs/latest/design

github.com/Softmotions/ejdb/blob/master/README.md

planetscale.com/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation and contributors

Softmotions

PlanetScale

Facebook, Inc.

Initial release

2012

2020

2013

Current release

29.0.1, April 2024

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

GPLv2

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

C++

Server operating systems

Linux
OS X
Unix

server-less

Docker
Linux
macOS

Linux

Data scheme

yes

schema-less columns are supported

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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 for querying

yes

with proprietary extensions

APIs and other access methods

JDBC
RESTful HTTP/JSON API

in-process shared library

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
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

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

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

ACID at shard level

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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.