DBMS > Riak TS vs. RocksDB vs. Tkrzw vs. Vitess

System Properties Comparison Riak TS vs. RocksDB vs. Tkrzw vs. Vitess

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

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

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Time Series DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
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	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

rocksdb.org

dbmx.net/tkrzw

vitess.io

Technical documentation

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

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

Open Source, formerly Basho Technologies

Facebook, Inc.

Mikio Hirabayashi

The Linux Foundation, PlanetScale

Initial release

2015

2013

2020

2013

Current release

3.0.0, September 2022

8.11.4, April 2024

0.9.3, August 2020

15.0.2, December 2022

License

Commercial or Open Source

Open Source

BSD

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0, commercial licenses available

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

Server operating systems

Linux
OS X

Linux

Linux
macOS

Docker
Linux
macOS

Data scheme

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

with proprietary extensions

APIs and other access methods

HTTP API
Native Erlang Interface

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Erlang

yes

proprietary syntax

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

none

Multi-source replication
Source-replica replication

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 across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

links between datasets can be stored

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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.