DBMS > Riak TS vs. RocksDB vs. Splunk vs. Tkrzw vs. Warp 10

System Properties Comparison Riak TS vs. RocksDB vs. Splunk vs. Tkrzw vs. Warp 10

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Analytics Platform for Big Data

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

Technical documentation

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

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

www.warp10.io/content/02_Getting_started

Developer

Open Source, formerly Basho Technologies

Facebook, Inc.

Splunk Inc.

Mikio Hirabayashi

SenX

Initial release

2015

2013

2003

2020

2015

Current release

3.0.0, September 2022

9.2.1, May 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

BSD

commercial

Limited free edition and free developer edition available

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Erlang

C++

Java

Server operating systems

Linux
OS X

Linux

Linux
OS X
Solaris
Windows

Linux
macOS

Linux
OS X
Windows

Data scheme

schema-free

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

restricted

yes

SQL

Support of SQL

yes, limited

Splunk Search Processing Language for search commands

APIs and other access methods

HTTP API
Native Erlang Interface

C++ API
Java API

HTTP REST

HTTP API
Jupyter
WebSocket

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++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

Erlang

yes

WarpScript

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Multi-source replication

none

selectable replication factor

based on HBase

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

based on HBase

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

yes

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

using specific database classes

yes

User concepts

Access control

Access rights for users and roles

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.