DBMS > RethinkDB vs. Riak TS vs. RocksDB vs. Teradata

System Properties Comparison RethinkDB vs. Riak TS vs. RocksDB vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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 hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.74
Rank	#105	Overall
	#19	Document stores

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

rethinkdb.com

rocksdb.org

www.teradata.com

Technical documentation

rethinkdb.com/docs

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

github.com/facebook/rocksdb/wiki

docs.teradata.com

Developer

The Linux Foundation

since July 2017

Open Source, formerly Basho Technologies

Facebook, Inc.

Teradata

Initial release

2009

2015

2013

1984

Current release

2.4.1, August 2020

3.0.0, September 2022

8.11.4, April 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

BSD

commercial

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

C++

Erlang

C++

Server operating systems

Linux
OS X
Windows

Linux
OS X

Linux

hosted
Linux

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.

yes

Secondary indexes

yes

restricted

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes, limited

yes

SQL 2016 + extensions

APIs and other access methods

HTTP API
Native Erlang Interface

C++ API
Java API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

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

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
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

Erlang

yes

UDFs, stored procedures, table functions in parallel

Triggers

Client-side triggers through changefeeds

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

range based

Sharding

horizontal partitioning

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

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

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

Atomic single-document operations

yes

ACID

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

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.