DBMS > Amazon DocumentDB vs. RocksDB vs. Splunk vs. ToroDB

System Properties Comparison Amazon DocumentDB vs. RocksDB vs. Splunk vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

Primary database model

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

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

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

aws.amazon.com/documentdb

rocksdb.org

www.splunk.com

github.com/torodb/server

Technical documentation

aws.amazon.com/documentdb/resources

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

Facebook, Inc.

Splunk Inc.

8Kdata

Initial release

2019

2013

2003

2016

Current release

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Limited free edition and free developer edition available

Open Source

AGPL-V3

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

Server operating systems

hosted

Linux

Linux
OS X
Solaris
Windows

All OS with a Java 7 VM

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

Splunk Search Processing Language for search commands

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

C++ API
Java API

HTTP REST

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

Atomic single-document operations

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

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.