DBMS > BoltDB vs. gStore vs. RocksDB vs. Splunk vs. Tarantool

System Properties Comparison BoltDB vs. gStore vs. RocksDB vs. Splunk vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

A native Graph DBMS to store and maintain very large RDF datasets.

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

Analytics Platform for Big Data

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

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

Score	0.14
Rank	#342	Overall
	#34	Graph DBMS
	#16	RDF stores

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

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

github.com/boltdb/bolt

Technical documentation

en.gstore.cn/#/enDocs

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

www.tarantool.io/en/doc

Developer

Facebook, Inc.

Splunk Inc.

Initial release

2013

2016

2013

2003

2008

Current release

1.2, November 2023

9.2.1, May 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

BSD

Open Source

BSD

commercial

Limited free edition and free developer edition available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Solaris
Windows

BSD
Linux
macOS

Data scheme

schema-free

schema-free and OWL/RDFS-schema support

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Full-featured ANSI SQL support

APIs and other access methods

HTTP API
SPARQL 1.1

C++ API
Java API

HTTP REST

Open binary protocol

Supported programming languages

C++
Java
JavaScript (Node.js)
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

Lua, C and SQL stored procedures

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Users, roles and permissions, Role-Based Access Control (RBAC) supported

Access rights for users and roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.