DBMS > BoltDB vs. GeoMesa vs. RocksDB vs. Rockset vs. Splunk

System Properties Comparison BoltDB vs. GeoMesa vs. RocksDB vs. Rockset vs. Splunk

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Analytics Platform for Big Data

Primary database model

Secondary database models

Relational DBMS
Search engine

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

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

github.com/boltdb/bolt

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

github.com/facebook/rocksdb/wiki

docs.rockset.com

docs.splunk.com/Documentation/Splunk

Developer

CCRi and others

Facebook, Inc.

Rockset

Splunk Inc.

Initial release

2013

2014

2013

2019

2003

Current release

5.0.0, May 2024

9.2.1, May 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache License 2.0

Open Source

BSD

commercial

Limited free edition and free developer edition available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

hosted

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

dynamic typing

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.

ingestion from XML files supported

yes

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

Read-only SQL queries, including JOINs

Splunk Search Processing Language for search commands

APIs and other access methods

C++ API
Java API

HTTP REST

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

horizontal partitioning

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

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

depending on storage layer

Eventual Consistency

Foreign keys

Referential integrity

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

Concurrency

Support for concurrent manipulation of data

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users and organizations can be defined via Rockset console

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.