DBMS > BoltDB vs. GeoMesa vs. RocksDB vs. Splunk vs. Valentina Server

System Properties Comparison BoltDB vs. GeoMesa vs. RocksDB vs. Splunk vs. Valentina Server

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)

Analytics Platform for Big Data

Object-relational database and reports server

Primary database model

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	89.10
Rank	#14	Overall
	#2	Search engines

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

github.com/boltdb/bolt

Technical documentation

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

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

CCRi and others

Facebook, Inc.

Splunk Inc.

Paradigma Software

Initial release

2013

2014

2013

2003

1999

Current release

5.0.0, May 2024

9.2.1, May 2024

5.7.5

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

commercial

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

Scala

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

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

SQL

Support of SQL

Splunk Search Processing Language for search commands

yes

APIs and other access methods

C++ API
Java API

HTTP REST

ODBC

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

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

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

yes

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 roles

fine grained access rights according to SQL-standard

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.