DBMS > RocksDB vs. SiteWhere vs. Splunk vs. TerarkDB

System Properties Comparison RocksDB vs. SiteWhere vs. Splunk vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

M2M integration platform for persisting/querying time series data

Analytics Platform for Big Data

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

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

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

Score	0.06
Rank	#367	Overall
	#36	Time Series DBMS

Score	88.71
Rank	#14	Overall
	#2	Search engines

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

rocksdb.org

github.com/sitewhere/sitewhere

www.splunk.com

github.com/bytedance/terarkdb

Technical documentation

github.com/facebook/rocksdb/wiki

sitewhere1.sitewhere.io/index.html

docs.splunk.com/Documentation/Splunk

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Facebook, Inc.

SiteWhere

Splunk Inc.

ByteDance, originally Terark

Initial release

2013

2010

2003

2016

Current release

8.11.4, April 2024

License

Commercial or Open Source

Open Source

BSD

Open Source

Common Public Attribution License Version 1.0

commercial

Limited free edition and free developer edition available

commercial

restricted open source version 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++

Java

C++

Server operating systems

Linux

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

Data scheme

schema-free

predefined scheme

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

yes

SQL

Support of SQL

Splunk Search Processing Language for search commands

APIs and other access methods

C++ API
Java API

HTTP REST

C++ API
Java API

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

based on HBase

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on HBase

Multi-source replication

none

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

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

User concepts

Access control

Users with fine-grained authorization concept

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.