DBMS > BoltDB vs. RocksDB vs. Splunk vs. Teradata vs. VoltDB

System Properties Comparison BoltDB vs. RocksDB vs. Splunk vs. Teradata vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

Analytics Platform for Big Data

A hybrid cloud data analytics software platform (Teradata Vantage)

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Key-value store

Search engine

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

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

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

github.com/boltdb/bolt

Technical documentation

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

docs.teradata.com

docs.voltdb.com

Developer

Facebook, Inc.

Splunk Inc.

Teradata

VoltDB Inc.

Initial release

2013

2003

1984

2010

Current release

8.11.4, April 2024

Teradata Vantage 1.0 MU2, January 2019

11.3, April 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

BSD

commercial

Limited free edition and free developer edition available

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

BSD
Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Solaris
Windows

hosted
Linux

Linux
OS X

for development

Data scheme

schema-free

yes

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

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

yes

SQL

Support of SQL

Splunk Search Processing Language for search commands

yes

SQL 2016 + extensions

yes

only a subset of SQL 99

APIs and other access methods

C++ API
Java API

HTTP REST

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

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

UDFs, stored procedures, table functions in parallel

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Hashing

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

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

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

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

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.