DBMS > Apache Druid vs. Heroic vs. RocksDB vs. Solr vs. Tigris

System Properties Comparison Apache Druid vs. Heroic vs. RocksDB vs. Solr vs. Tigris

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

A widely used distributed, scalable search engine based on Apache Lucene

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Relational DBMS
Time Series DBMS

Time Series DBMS

Key-value store

Search engine

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Spatial DBMS

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	0.51
Rank	#255	Overall
	#21	Time Series DBMS

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

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

druid.apache.org

github.com/spotify/heroic

rocksdb.org

solr.apache.org

www.tigrisdata.com

Technical documentation

druid.apache.org/docs/latest/design

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

www.tigrisdata.com/docs

Developer

Apache Software Foundation and contributors

Spotify

Facebook, Inc.

Apache Software Foundation

Tigris Data, Inc.

Initial release

2012

2014

2013

2006

2022

Current release

29.0.1, April 2024

8.11.4, April 2024

9.6.0, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache 2.0

Open Source

BSD

Open Source

Apache Version 2

Open Source

Apache Version 2.0

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

Server operating systems

Linux
OS X
Unix

Linux

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux
macOS
Windows

Data scheme

yes

schema-less columns are supported

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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 Elasticsearch

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL for querying

Solr Parallel SQL Interface

APIs and other access methods

JDBC
RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

C++ API
Java API

Java API
RESTful HTTP/JSON API

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

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.