DBMS > Microsoft Azure Table Storage vs. Riak TS vs. SAP HANA vs. TerminusDB vs. Transbase

System Properties Comparison Microsoft Azure Table Storage vs. Riak TS vs. SAP HANA vs. TerminusDB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

A Wide Column Store for rapid development using massive semi-structured datasets

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
RDF store

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

azure.microsoft.com/en-us/services/storage/tables

www.sap.com/products/hana.html

terminusdb.com

www.transaction.de/en/products/transbase.html

Technical documentation

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

help.sap.com/hana

terminusdb.github.io/terminusdb/#

www.transaction.de/en/products/transbase/features.html

Developer

Microsoft

Open Source, formerly Basho Technologies

SAP

DataChemist Ltd.

Transaction Software GmbH

Initial release

2012

2015

2010

2018

1987

Current release

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

11.0.0, January 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

commercial

Open Source

GPL V3

commercial

free development license

Cloud-based only

Only available as a cloud service

yes

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

Prolog, Rust

C and C++

Server operating systems

hosted

Linux
OS X

Appliance or cloud-service

Linux

FreeBSD
Linux
macOS
Solaris
Windows

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

restricted

yes

SQL

Support of SQL

yes, limited

yes

SQL-like query language (WOQL)

yes

APIs and other access methods

RESTful HTTP API

HTTP API
Native Erlang Interface

JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

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

JavaScript
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

Erlang

SQLScript, R

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

selectable replication factor

yes

Journaling Streams

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

optimistic locking

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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 based on private key authentication or shared access signatures

yes

Role-based access control

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.