DBMS > Apache Druid vs. Datomic vs. PouchDB vs. RocksDB vs. Splunk

System Properties Comparison Apache Druid vs. Datomic vs. PouchDB vs. RocksDB vs. Splunk

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

JavaScript DBMS with an API inspired by CouchDB

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

Analytics Platform for Big Data

Primary database model

Relational DBMS
Time Series DBMS

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

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

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

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

Technical documentation

druid.apache.org/docs/latest/design

docs.datomic.com

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation and contributors

Cognitect

Apache Software Foundation

Facebook, Inc.

Splunk Inc.

Initial release

2012

2013

2003

Current release

29.0.1, April 2024

1.0.7075, December 2023

7.1.1, June 2019

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

limited edition free

Open Source

BSD

commercial

Limited free edition and free developer edition available

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

Java, Clojure

JavaScript

C++

Server operating systems

Linux
OS X
Unix

All OS with a Java VM

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-less columns are supported

yes

schema-free

yes

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.

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL for querying

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
RESTful HTTP/JSON API

RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

HTTP REST

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Clojure
Java

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

View functions in JavaScript

yes

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

But extensive use of caching in the application peers

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

none

But extensive use of caching in the application peers

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

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

Access rights for users and 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.