DBMS > BoltDB vs. Brytlyt vs. RocksDB vs. Splunk vs. TerminusDB

System Properties Comparison BoltDB vs. Brytlyt vs. RocksDB vs. Splunk vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

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

Analytics Platform for Big Data

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
RDF store

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

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

Score	0.38
Rank	#279	Overall
	#126	Relational DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	88.71
Rank	#14	Overall
	#2	Search engines

Score	0.22
Rank	#323	Overall
	#28	Graph DBMS

Website

github.com/boltdb/bolt

Technical documentation

docs.brytlyt.io

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

terminusdb.github.io/terminusdb/#

Developer

Brytlyt

Facebook, Inc.

Splunk Inc.

DataChemist Ltd.

Initial release

2013

2016

2013

2003

2018

Current release

5.0, August 2023

8.11.4, April 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

BSD

commercial

Limited free edition and free developer edition available

Open Source

GPL V3

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 CUDA

C++

Prolog, Rust

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Linux

Linux
OS X
Solaris
Windows

Linux

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

C++ API
Java API

HTTP REST

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

Multi-source replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

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

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

Role-based access control

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.