DBMS > BoltDB vs. GridGain vs. QuestDB vs. RocksDB vs. Splunk

System Properties Comparison BoltDB vs. GridGain vs. QuestDB vs. RocksDB vs. Splunk

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

GridGain is an in-memory computing platform, built on Apache Ignite

A high performance open source SQL database for time series data

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

Analytics Platform for Big Data

Primary database model

Key-value store

Key-value store
Relational DBMS

Time Series DBMS

Key-value store

Search engine

Secondary database models

Relational DBMS

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

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

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	2.52
Rank	#109	Overall
	#9	Time Series DBMS

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

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

github.com/boltdb/bolt

Technical documentation

www.gridgain.com/docs/index.html

questdb.io/docs

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

GridGain Systems, Inc.

QuestDB Technology Inc

Facebook, Inc.

Splunk Inc.

Initial release

2013

2007

2014

2013

2003

Current release

GridGain 8.5.1

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Apache 2.0

Open Source

BSD

commercial

Limited free edition and free developer edition available

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

Java, C++, .Net

Java (Zero-GC), C++, Rust

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free via InfluxDB Line Protocol

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

ANSI-99 for query and DML statements, subset of DDL

SQL with time-series extensions

Splunk Search Processing Language for search commands

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

C++ API
Java API

HTTP REST

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning (by timestamps)

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes (replicated cache)

Source-replica replication with eventual consistency

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

ACID

ACID for single-table writes

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.

yes

through memory mapped files

yes

User concepts

Access control

Security Hooks for custom implementations

Access rights for users and roles

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

Create an IoT server with QuestDB and a Raspberry Pi
4 April 2024

TimescaleDB vs. QuestDB: Performance benchmarks and overview
27 March 2024

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.