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

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

Editorial information provided by DB-Engines

Name

Description

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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

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

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

Score	2.28
Rank	#115	Overall
	#21	Document stores

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

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

github.com/boltdb/bolt

Technical documentation

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

docs.stardog.com

Developer

Apache Software Foundation

Facebook, Inc.

Splunk Inc.

Stardog-Union

Initial release

2013

2012

2013

2003

2010

Current release

7.1.1, June 2019

8.11.4, April 2024

7.3.0, May 2020

License

Commercial or Open Source

Open Source

MIT License

Open Source

BSD

commercial

Limited free edition and free developer edition available

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

JavaScript

C++

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

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

Linux

Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free and OWL/RDFS-schema support

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

Import/export of XML data possible

Secondary indexes

yes

via views

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

Splunk Search Processing Language for search commands

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

HTTP REST

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

Multi-source replication

Multi-source replication in HA-Cluster

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 in HA-Cluster

Foreign keys

Referential integrity

yes

relationships in graphs

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

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.