DBMS > IRONdb vs. Riak TS vs. SAP HANA vs. SwayDB vs. Transbase

System Properties Comparison IRONdb vs. Riak TS vs. SAP HANA vs. SwayDB vs. Transbase

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

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

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.00
Rank	#382	Overall
	#59	Key-value stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.circonus.com/solutions/time-series-database/

www.sap.com/products/hana.html

swaydb.simer.au

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

Technical documentation

docs.circonus.com/irondb/category/getting-started

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

help.sap.com/hana

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

Developer

Circonus LLC.

Open Source, formerly Basho Technologies

SAP

Simer Plaha

Transaction Software GmbH

Initial release

2017

2015

2010

2018

1987

Current release

V0.10.20, January 2018

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

commercial

Open Source

GNU Affero GPL V3.0

commercial

free development 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

C and C++

Erlang

Scala

C and C++

Server operating systems

Linux

Linux
OS X

Appliance or cloud-service

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes, limited

yes

APIs and other access methods

HTTP API

HTTP API
Native Erlang Interface

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

Java
Kotlin
Scala

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

Server-side scripts

Stored procedures

yes, in Lua

Erlang

SQLScript, R

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

selectable replication factor

yes

none

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 per node, eventual consistency across nodes

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

Atomic execution of operations

yes

Concurrency

Support for concurrent manipulation of data

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

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.