DBMS > Blueflood vs. Riak TS vs. SAP HANA vs. SwayDB vs. TigerGraph

System Properties Comparison Blueflood vs. Riak TS vs. SAP HANA vs. SwayDB vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

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 complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

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.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

blueflood.io

www.sap.com/products/hana.html

swaydb.simer.au

www.tigergraph.com

Technical documentation

github.com/rax-maas/blueflood/wiki

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

help.sap.com/hana

docs.tigergraph.com

Developer

Rackspace

Open Source, formerly Basho Technologies

SAP

Simer Plaha

Initial release

2013

2015

2010

2018

2017

Current release

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

commercial

Open Source

GNU Affero GPL V3.0

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

Java

Erlang

Scala

C++

Server operating systems

Linux
OS X

Appliance or cloud-service

Linux

Data scheme

predefined 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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes, limited

yes

SQL-like query language (GSQL)

APIs and other access methods

HTTP REST

HTTP API
Native Erlang Interface

JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

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

Java
Kotlin
Scala

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

based on Cassandra

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between datasets can be stored

yes

Relationships in graphs

Transaction concepts

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

ACID

Atomic execution of operations

ACID

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

Role-based access control

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.