DBMS > Apache Druid vs. Apache IoTDB vs. BoltDB vs. RocksDB vs. Splunk

System Properties Comparison Apache Druid vs. Apache IoTDB vs. BoltDB 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

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

An embedded key-value store for Go.

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

Time Series DBMS

Key-value store

Search engine

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	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

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

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

druid.apache.org

iotdb.apache.org

github.com/boltdb/bolt

rocksdb.org

www.splunk.com

Technical documentation

druid.apache.org/docs/latest/design

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation and contributors

Apache Software Foundation

Facebook, Inc.

Splunk Inc.

Initial release

2012

2018

2013

2003

Current release

29.0.1, April 2024

1.1.0, April 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache Version 2.0

Open Source

MIT License

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

C++

Server operating systems

Linux
OS X
Unix

All OS with a Java VM (>= 1.8)

BSD
Linux
OS X
Solaris
Windows

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

SQL

Support of SQL

SQL for querying

SQL-like query language

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
RESTful HTTP/JSON API

JDBC
Native API

C++ API
Java API

HTTP REST

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C
C#
C++
Go
Java
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

none

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong Consistency with Raft

none

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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

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

yes

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.