DBMS > RocksDB vs. Splunk vs. STSdb vs. UniData,UniVerse vs. Vitess

System Properties Comparison RocksDB vs. Splunk vs. STSdb vs. UniData,UniVerse vs. Vitess

Editorial information provided by DB-Engines

Name

Description

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

Analytics Platform for Big Data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

MultiValue database and application server with SQL mapping layer and meta database capabilities

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

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

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	3.16
Rank	#97	Overall
	#2	Multivalue DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

rocksdb.org

www.splunk.com

github.com/STSSoft/STSdb4

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

vitess.io

Technical documentation

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

vitess.io/docs

Developer

Facebook, Inc.

Splunk Inc.

STS Soft SC

Rocket Software

The Linux Foundation, PlanetScale

Initial release

2013

2003

2011

1985

2013

Current release

8.11.4, April 2024

4.0.8, September 2015

15.0.2, December 2022

License

Commercial or Open Source

Open Source

BSD

commercial

Limited free edition and free developer edition available

Open Source

GPLv2, commercial license available

commercial

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

C++

Server operating systems

Linux

Linux
OS X
Solaris
Windows

Windows

AIX
HP-UX
Linux
Solaris
Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

optional

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

yes

with proprietary extensions

APIs and other access methods

C++ API
Java API

HTTP REST

.NET Client API

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C#
Java

.Net
Basic

U2 Basic
C
Java

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

yes

proprietary syntax

Triggers

yes

U2 Basic

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

none

Source-replica replication

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

ACID

configurable

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

User concepts

Access control

Access rights for users and roles

Access rights according to SQL-standard and operating system based

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.