DBMS > Ehcache vs. Heroic vs. OpenQM vs. Riak TS

System Properties Comparison Ehcache vs. Heroic vs. OpenQM vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

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

Primary database model

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

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

www.ehcache.org

github.com/spotify/heroic

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

Technical documentation

www.ehcache.org/documentation

spotify.github.io/heroic

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

Developer

Terracotta Inc, owned by Software AG

Spotify

Rocket Software, originally Martin Phillips

Open Source, formerly Basho Technologies

Initial release

2009

2014

1993

2015

Current release

3.10.0, March 2022

3.4-12

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

GPLv2, extended commercial license available

Open Source

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

Server operating systems

All OS with a Java VM

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
OS X

Data scheme

schema-free

yes

with some exceptions

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

restricted

SQL

Support of SQL

yes, limited

APIs and other access methods

JCache

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

HTTP API
Native Erlang Interface

Supported programming languages

Java

.Net
Basic
C
Java
Objective C
PHP
Python

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

Server-side scripts

Stored procedures

yes

Erlang

Triggers

yes

Cache Event Listeners

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

Access rights can be defined down to the item level

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Scaling Australia's Most Popular Online News Sites with Ehcache
6 December 2010, InfoQ.com

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, dzone.com

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Share this page