DBMS > BoltDB vs. Dragonfly vs. H2 vs. RocksDB vs. Splunk

System Properties Comparison BoltDB vs. Dragonfly vs. H2 vs. RocksDB vs. Splunk

Editorial information provided by DB-Engines

Name

Description

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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	0.76
Rank	#224	Overall
	#32	Key-value stores

Score	0.42
Rank	#271	Overall
	#38	Key-value stores

Score	8.22
Rank	#50	Overall
	#32	Relational DBMS

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

Score	88.71
Rank	#14	Overall
	#2	Search engines

Website

github.com/boltdb/bolt

github.com/dragonflydb/dragonfly
www.dragonflydb.io

www.h2database.com

rocksdb.org

www.splunk.com

Technical documentation

www.dragonflydb.io/docs

www.h2database.com/html/main.html

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

DragonflyDB team and community contributors

Thomas Mueller

Facebook, Inc.

Splunk Inc.

Initial release

2013

2023

2005

2013

2003

Current release

1.0, March 2023

2.2.220, July 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

BSL 1.1

Open Source

dual-licence (Mozilla public license, Eclipse public license)

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++

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

All OS with a Java VM

Linux

Linux
OS X
Solaris
Windows

Data scheme

schema-free

scheme-free

yes

schema-free

yes

Typing

predefined data types such as float or date

strings, hashes, lists, sets, sorted sets, bit arrays

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

Proprietary protocol

RESP - REdis Serialization Protocol

JDBC
ODBC

C++ API
Java API

HTTP REST

Supported programming languages

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

Java

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

Java Stored Procedures and User-Defined Functions

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

With clustering: 2 database servers on different computers operate on identical copies of a database

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

none

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Atomic execution of command blocks and scripts

ACID

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

yes, strict serializability by the server

yes, multi-version concurrency control (MVCC)

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

Password-based authentication

fine grained access rights according to SQL-standard

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.