DBMS > Amazon DocumentDB vs. Apache Druid vs. Badger vs. EJDB vs. RocksDB

System Properties Comparison Amazon DocumentDB vs. Apache Druid vs. Badger vs. EJDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

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

Primary database model

Document store

Relational DBMS
Time Series DBMS

Key-value store

Document store

Key-value store

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	0.31
Rank	#296	Overall
	#44	Document stores

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

Website

aws.amazon.com/documentdb

druid.apache.org

github.com/dgraph-io/badger

github.com/Softmotions/ejdb

rocksdb.org

Technical documentation

aws.amazon.com/documentdb/resources

druid.apache.org/docs/latest/design

godoc.org/github.com/dgraph-io/badger

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

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation and contributors

DGraph Labs

Softmotions

Facebook, Inc.

Initial release

2019

2012

2017

2012

2013

Current release

29.0.1, April 2024

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache license v2

Open Source

Apache 2.0

Open Source

GPLv2

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

hosted

Linux
OS X
Unix

BSD
Linux
OS X
Solaris
Windows

server-less

Linux

Data scheme

schema-free

yes

schema-less columns are supported

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
RESTful HTTP/JSON API

in-process shared library

C++ API
Java API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

manual/auto, time-based

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes, via HDFS, S3 or other storage engines

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

Atomic single-document operations

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

User concepts

Access control

Access rights for users and roles

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

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.