DBMS > Heroic vs. Quasardb vs. RethinkDB vs. RocksDB

System Properties Comparison Heroic vs. Quasardb vs. RethinkDB vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Distributed, high-performance timeseries database

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

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

Primary database model

Time Series DBMS

Document store

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	2.74
Rank	#105	Overall
	#19	Document stores

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

Website

github.com/spotify/heroic

quasar.ai

rethinkdb.com

rocksdb.org

Technical documentation

spotify.github.io/heroic

doc.quasar.ai/master

rethinkdb.com/docs

github.com/facebook/rocksdb/wiki

Developer

Spotify

quasardb

The Linux Foundation

since July 2017

Facebook, Inc.

Initial release

2014

2009

2013

Current release

3.14.1, January 2024

2.4.1, August 2020

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Apache Version 2

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++

Server operating systems

BSD
Linux
OS X
Windows

Linux
OS X
Windows

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

yes

string, binary, float, bool, date, geometry

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

with tags

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

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

HTTP API

C++ API
Java API

Supported programming languages

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Triggers

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

Sharding

range based

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication with selectable replication factor

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Atomic single-document operations

yes

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

Cryptographically strong user authentication and audit trail

yes

users and table-level permissions

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.