DBMS > Apache Druid vs. Elasticsearch vs. Oracle Berkeley DB vs. OrigoDB vs. RocksDB

System Properties Comparison Apache Druid vs. Elasticsearch vs. Oracle Berkeley DB vs. OrigoDB vs. RocksDB

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

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Widely used in-process key-value store

A fully ACID in-memory object graph database

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

Primary database model

Relational DBMS
Time Series DBMS

Search engine

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store
Object oriented DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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	134.78
Rank	#7	Overall
	#1	Search engines

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

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

Website

druid.apache.org

www.elastic.co/elasticsearch

www.oracle.com/database/technologies/related/berkeleydb.html

origodb.com

rocksdb.org

Technical documentation

druid.apache.org/docs/latest/design

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

docs.oracle.com/cd/E17076_05/html/index.html

origodb.com/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation and contributors

Elastic

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Robert Friberg et al

Facebook, Inc.

Initial release

2012

2010

1994

2009

under the name LiveDB

2013

Current release

29.0.1, April 2024

8.6, January 2023

18.1.40, May 2020

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Elastic License

Open Source

commercial license 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, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

Linux
OS X
Unix

All OS with a Java VM

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
Windows

Linux

Data scheme

yes

schema-less columns are supported

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

only with the Berkeley DB XML edition

can be achieved using .NET

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL for querying

SQL-like query language

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
RESTful HTTP/JSON API

Java API
RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

.Net

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

yes

only for the SQL API

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Foreign keys

Referential integrity

depending on model

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

yes

Write ahead log

yes

In-memory capabilities

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

Memcached and Redis integration

yes

User concepts

Access control

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

Role based authorization

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.