DBMS > GigaSpaces vs. RocksDB vs. Splunk vs. ToroDB vs. Transbase

System Properties Comparison GigaSpaces vs. RocksDB vs. Splunk vs. ToroDB vs. Transbase

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

Analytics Platform for Big Data

A MongoDB-compatible JSON document store, built on top of PostgreSQL

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Object oriented DBMS

Values are user defined objects

Secondary database models

Graph DBMS
Search engine

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

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

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

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.gigaspaces.com

rocksdb.org

www.splunk.com

github.com/torodb/server

www.transaction.de/en/products/transbase.html

Technical documentation

docs.gigaspaces.com/latest/landing.html

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

www.transaction.de/en/products/transbase/features.html

Developer

Gigaspaces Technologies

Facebook, Inc.

Splunk Inc.

8Kdata

Transaction Software GmbH

Initial release

2000

2013

2003

2016

1987

Current release

15.5, September 2020

8.11.4, April 2024

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2; Commercial licenses available

Open Source

BSD

commercial

Limited free edition and free developer edition available

Open Source

AGPL-V3

commercial

free development license

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

Java

C and C++

Server operating systems

Linux
macOS
Solaris
Windows

Linux

Linux
OS X
Solaris
Windows

All OS with a Java 7 VM

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

Splunk Search Processing Language for search commands

yes

APIs and other access methods

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

C++ API
Java API

HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C++
Java
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes, event driven architecture

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

Multi-source replication

Source-replica 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

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

yes

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

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.