DBMS > Heroic vs. Oracle Coherence vs. Riak TS vs. RocksDB vs. Warp 10

System Properties Comparison Heroic vs. Oracle Coherence vs. Riak TS vs. RocksDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

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

Oracles in-memory data grid solution

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

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

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

github.com/spotify/heroic

www.oracle.com/java/coherence

rocksdb.org

www.warp10.io

Technical documentation

spotify.github.io/heroic

docs.oracle.com/en/middleware/standalone/coherence

www.tiot.jp/riak-docs/riak/ts/latest

github.com/facebook/rocksdb/wiki

www.warp10.io/content/02_Getting_started

Developer

Spotify

Oracle

Open Source, formerly Basho Technologies

Facebook, Inc.

SenX

Initial release

2014

2007

2015

2013

2015

Current release

14.1, August 2023

3.0.0, September 2022

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

BSD

Open Source

Apache License 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

Erlang

C++

Java

Server operating systems

All OS with a Java VM

Linux
OS X

Linux

Linux
OS X
Windows

Data scheme

schema-free

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

restricted

SQL

Support of SQL

yes, limited

APIs and other access methods

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

JCache
JPA
RESTful HTTP API

HTTP API
Native Erlang Interface

C++ API
Java API

HTTP API
Jupyter
WebSocket

Supported programming languages

.Net
C++
Java

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Erlang

yes

WarpScript

Triggers

yes

Live Events

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, with selectable consistency level

selectable replication factor

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

configurable

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optionally

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

authentification to access the cache via certificates or http basic authentication

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.