DBMS > BoltDB vs. GigaSpaces vs. PostGIS vs. RocksDB vs. Splunk

System Properties Comparison BoltDB vs. GigaSpaces vs. PostGIS vs. RocksDB vs. Splunk

Editorial information provided by DB-Engines

Name

Description

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Spatial extension of PostgreSQL

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

Analytics Platform for Big Data

Primary database model

Key-value store

Document store
Object oriented DBMS

Values are user defined objects

Spatial DBMS

Key-value store

Search engine

Secondary database models

Graph DBMS
Search engine

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	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial 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

docs.gigaspaces.com/latest/landing.html

postgis.net/documentation

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

Gigaspaces Technologies

Facebook, Inc.

Splunk Inc.

Initial release

2013

2000

2005

2013

2003

Current release

15.5, September 2020

3.4.2, February 2024

9.2.1, May 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; Commercial licenses available

Open Source

GPL v2.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

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Solaris
Windows

Linux

Linux
OS X
Solaris
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.

XML can be used for describing objects metadata

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

yes

Splunk Search Processing Language for search commands

APIs and other access methods

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

C++ API
Java API

HTTP REST

Supported programming languages

.Net
C++
Java
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes, event driven architecture

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

based on PostgreSQL

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

based on PostgreSQL

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

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

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

User concepts

Access control

Role-based access control

yes

based on PostgreSQL

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.