DBMS > CouchDB vs. Heroic vs. Riak TS vs. SAP HANA

System Properties Comparison CouchDB vs. Heroic vs. Riak TS vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

couchdb.apache.org

github.com/spotify/heroic

www.sap.com/products/hana.html

Technical documentation

docs.couchdb.org/en/stable

spotify.github.io/heroic

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

help.sap.com/hana

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Spotify

Open Source, formerly Basho Technologies

SAP

Initial release

2005

2014

2015

2010

Current release

3.3.3, December 2023

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache 2.0

Open Source

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

Java

Erlang

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
OS X

Appliance or cloud-service

Data scheme

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 views

yes

via Elasticsearch

restricted

yes

SQL

Support of SQL

yes, limited

yes

APIs and other access methods

RESTful HTTP/JSON API

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

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

View functions in JavaScript

Erlang

SQLScript, R

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between datasets can be stored

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

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 for users can be defined per database

yes

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.