DBMS > Heroic vs. PostGIS vs. Riak KV vs. RocksDB vs. TimesTen

System Properties Comparison Heroic vs. PostGIS vs. Riak KV vs. RocksDB vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

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

Spatial extension of PostgreSQL

Distributed, fault tolerant key-value store

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

In-Memory RDBMS compatible to Oracle

Primary database model

Time Series DBMS

Spatial DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Key-value store

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

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

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

github.com/spotify/heroic

postgis.net

rocksdb.org

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

spotify.github.io/heroic

postgis.net/documentation

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

github.com/facebook/rocksdb/wiki

docs.oracle.com/database/timesten-18.1

Developer

Spotify

OpenSource, formerly Basho Technologies

Facebook, Inc.

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2014

2005

2009

2013

1998

Current release

3.4.2, February 2024

3.2.0, December 2022

9.2.1, May 2024

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL v2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

BSD

commercial

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

Server operating systems

Linux
OS X

Linux

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

yes

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

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

HTTP API
Native Erlang Interface

C++ API
Java API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

user defined functions

Erlang

PL/SQL

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Sharding

no "single point of failure"

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

selectable replication factor

yes

Multi-source replication
Source-replica replication

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

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

In-memory capabilities

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

yes

User concepts

Access control

yes

based on PostgreSQL

yes, using Riak Security

fine grained access rights according to SQL-standard

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.