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

System Properties Comparison Apache Druid vs. EJDB vs. MarkLogic 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)

Operational and transactional Enterprise NoSQL database

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

Primary database model

Relational DBMS
Time Series DBMS

Document store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

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

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	0.30
Rank	#294	Overall
	#44	Document stores

Score	6.50
Rank	#56	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#5	Search engines

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

Website

druid.apache.org

github.com/Softmotions/ejdb

www.marklogic.com

rocksdb.org

Technical documentation

druid.apache.org/docs/latest/design

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

docs.marklogic.com

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation and contributors

Softmotions

MarkLogic Corp.

Facebook, Inc.

Initial release

2012

2001

2013

Current release

29.0.1, April 2024

11.0, December 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

GPLv2

commercial

restricted free version is available

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

C++

Server operating systems

Linux
OS X
Unix

server-less

Linux
OS X
Windows

Linux

Data scheme

yes

schema-less columns are supported

schema-free

Schema can be enforced

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

yes

SQL92

APIs and other access methods

JDBC
RESTful HTTP/JSON API

in-process shared library

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

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

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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, with Range Indexes

yes

User concepts

Access control

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

Role-based access control at the document and subdocument levels

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.