DBMS > Apache Druid vs. Heroic vs. RocksDB vs. Titan

System Properties Comparison Apache Druid vs. Heroic vs. RocksDB vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

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)

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Relational DBMS
Time Series DBMS

Time Series DBMS

Key-value store

Graph 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

Website

druid.apache.org

github.com/spotify/heroic

rocksdb.org

github.com/thinkaurelius/titan

Technical documentation

druid.apache.org/docs/latest/design

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

github.com/thinkaurelius/titan/wiki

Developer

Apache Software Foundation and contributors

Spotify

Facebook, Inc.

Aurelius, owned by DataStax

Initial release

2012

2014

2013

2012

Current release

29.0.1, April 2024

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache 2.0

Open Source

BSD

Open Source

Apache license, 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

Linux
OS X
Unix
Windows

Data scheme

yes

schema-less columns are supported

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL for querying

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
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

Clojure
Java
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

horizontal partitioning

yes

via pluggable storage backends

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

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

User authentification and security via Rexster Graph Server

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.