DBMS > BoltDB vs. KeyDB vs. PouchDB vs. RocksDB vs. Splunk

System Properties Comparison BoltDB vs. KeyDB vs. PouchDB vs. RocksDB vs. Splunk

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

JavaScript DBMS with an API inspired by CouchDB

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

Analytics Platform for Big Data

Primary database model

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

Score	0.76
Rank	#224	Overall
	#32	Key-value stores

Score	0.80
Rank	#219	Overall
	#31	Key-value stores

Score	2.35
Rank	#116	Overall
	#22	Document stores

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/Snapchat/KeyDB
keydb.dev

pouchdb.com

rocksdb.org

www.splunk.com

Technical documentation

docs.keydb.dev

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

EQ Alpha Technology Ltd.

Apache Software Foundation

Facebook, Inc.

Splunk Inc.

Initial release

2013

2019

2012

2013

2003

Current release

7.1.1, June 2019

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

BSD-3

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

JavaScript

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

via views

yes

SQL

Support of SQL

Splunk Search Processing Language for search commands

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

HTTP REST

Supported programming languages

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

View functions in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

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
Strong eventual consistency with CRDTs

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

Optimistic locking, atomic execution of commands blocks and scripts

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

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

simple password-based access control and ACL

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.