DBMS > Heroic vs. Riak TS vs. Snowflake vs. WakandaDB vs. Yanza

System Properties Comparison Heroic vs. Riak TS vs. Snowflake vs. WakandaDB vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

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

Cloud-based data warehousing service for structured and semi-structured data

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Time Series DBMS for IoT Applications

Primary database model

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

github.com/spotify/heroic

www.snowflake.com

wakanda.github.io

yanza.com

Technical documentation

spotify.github.io/heroic

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

docs.snowflake.net/manuals/index.html

wakanda.github.io/doc

Developer

Spotify

Open Source, formerly Basho Technologies

Snowflake Computing Inc.

Wakanda SAS

Yanza

Initial release

2014

2015

2014

2012

2015

Current release

3.0.0, September 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

commercial

Open Source

AGPLv3, extended commercial license available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Erlang

C++, JavaScript

Server operating systems

Linux
OS X

hosted

Linux
OS X
Windows

Windows

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

schema-free

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.

yes

Secondary indexes

yes

via Elasticsearch

restricted

SQL

Support of SQL

yes, limited

yes

APIs and other access methods

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

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

RESTful HTTP API

HTTP 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

JavaScript (Node.js)
Python

JavaScript

any language that supports HTTP calls

Server-side scripts

Stored procedures

Erlang

user defined functions

yes

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

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.

User concepts

Access control

Users with fine-grained authorization concept, user roles and pluggable authentication

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.