DBMS > Atos Standard Common Repository vs. BoltDB vs. GridGain vs. RocksDB vs. Splunk

System Properties Comparison Atos Standard Common Repository vs. BoltDB vs. GridGain vs. RocksDB vs. Splunk

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

An embedded key-value store for Go.

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

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

Analytics Platform for Big Data

Primary database model

Document store
Key-value store

Key-value store

Key-value store
Relational DBMS

Key-value store

Search engine

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	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

github.com/boltdb/bolt

www.gridgain.com

rocksdb.org

www.splunk.com

Technical documentation

www.gridgain.com/docs/index.html

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

Atos Convergence Creators

GridGain Systems, Inc.

Facebook, Inc.

Splunk Inc.

Initial release

2016

2013

2007

2013

2003

Current release

1703

GridGain 8.5.1

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

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

Java, C++, .Net

C++

Server operating systems

Linux

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

optional

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

Splunk Search Processing Language for search commands

APIs and other access methods

LDAP

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

C++ API
Java API

HTTP REST

Supported programming languages

All languages with LDAP bindings

C#
C++
Java
PHP
Python
Ruby
Scala

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

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes (replicated cache)

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

Immediate Consistency or Eventual Consistency depending on configuration

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

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

LDAP bind authentication

Security Hooks for custom implementations

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.