DBMS > RethinkDB vs. RisingWave vs. RocksDB vs. Splunk

System Properties Comparison RethinkDB vs. RisingWave vs. RocksDB vs. Splunk

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.

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

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

Analytics Platform for Big Data

Primary database model

Secondary database models

Spatial DBMS

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

Score	2.66
Rank	#107	Overall
	#20	Document stores

Score	0.64
Rank	#238	Overall
	#110	Relational DBMS

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

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

rethinkdb.com

www.risingwave.com/database

rocksdb.org

www.splunk.com

Technical documentation

rethinkdb.com/docs

docs.risingwave.com/docs/current/intro

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

The Linux Foundation

since July 2017

RisingWave Labs

Facebook, Inc.

Splunk Inc.

Initial release

2009

2022

2013

2003

Current release

2.4.1, August 2020

1.2, September 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

Open Source

BSD

commercial

Limited free edition and free developer edition 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

C++

Rust

C++

Server operating systems

Linux
OS X
Windows

Docker
Linux
macOS

Linux

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

Standard SQL-types and JSON

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

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
PostgreSQL wire protocol

C++ API
Java API

HTTP REST

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

Go
Java
JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

UDFs in Python or Java

yes

Triggers

Client-side triggers through changefeeds

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

range based

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

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

Foreign keys

Referential integrity

Transaction concepts

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

Atomic single-document operations

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

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

Users and Roles

Access rights for users and 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.