DBMS > KairosDB vs. RethinkDB vs. RocksDB vs. Transbase

System Properties Comparison KairosDB vs. RethinkDB vs. RocksDB vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Time Series DBMS based on Cassandra or H2

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Spatial DBMS

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

Score	0.71
Rank	#230	Overall
	#20	Time Series DBMS

Score	2.84
Rank	#106	Overall
	#19	Document stores

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

github.com/kairosdb/kairosdb

rethinkdb.com

rocksdb.org

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

Technical documentation

kairosdb.github.io

rethinkdb.com/docs

github.com/facebook/rocksdb/wiki

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

Developer

The Linux Foundation

since July 2017

Facebook, Inc.

Transaction Software GmbH

Initial release

2013

2009

2013

1987

Current release

1.2.2, November 2018

2.4.1, August 2020

8.11.4, April 2024

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2

Open Source

BSD

commercial

free development license

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

Java

C++

C and C++

Server operating systems

Linux
OS X
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

yes

SQL

Support of SQL

yes

APIs and other access methods

Graphite protocol
HTTP REST
Telnet API

C++ API
Java API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

C
C++
Go
Java
Perl
Python
Ruby

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

Server-side scripts

Stored procedures

yes

Triggers

Client-side triggers through changefeeds

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

range based

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Source-replica replication

yes

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

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-document operations

yes

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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

simple password-based access control

yes

users and table-level permissions

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.