DBMS > Riak TS vs. SAP HANA vs. Transbase vs. XTDB

System Properties Comparison Riak TS vs. SAP HANA vs. Transbase vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Time Series DBMS

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.sap.com/products/hana.html

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

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

help.sap.com/hana

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

www.xtdb.com/docs

Developer

Open Source, formerly Basho Technologies

SAP

Transaction Software GmbH

Juxt Ltd.

Initial release

2015

2010

1987

2019

Current release

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

Transbase 8.3, 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

commercial

free development license

Open Source

MIT License

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

C and C++

Clojure

Server operating systems

Linux
OS X

Appliance or cloud-service

FreeBSD
Linux
macOS
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

HTTP API
Native Erlang Interface

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
JDBC

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#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Clojure
Java

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

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Source-replica replication

yes, each node contains all data

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

Foreign keys

Referential integrity

links between datasets 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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

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.