DBMS > Amazon CloudSearch vs. Oracle Berkeley DB vs. RocksDB vs. Splunk vs. Transbase

System Properties Comparison Amazon CloudSearch vs. Oracle Berkeley DB vs. RocksDB vs. Splunk vs. Transbase

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

Widely used in-process key-value store

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

Analytics Platform for Big Data

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

Primary database model

Search engine

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Search engine

Relational DBMS

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

Score	1.81
Rank	#137	Overall
	#12	Search engines

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

aws.amazon.com/cloudsearch

www.oracle.com/database/technologies/related/berkeleydb.html

rocksdb.org

www.splunk.com

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

Technical documentation

docs.aws.amazon.com/cloudsearch

docs.oracle.com/cd/E17076_05/html/index.html

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

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

Developer

Amazon

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Splunk Inc.

Transaction Software GmbH

Initial release

2012

1994

2013

2003

1987

Current release

18.1.40, May 2020

9.2.1, May 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

BSD

commercial

Limited free edition and free developer edition available

commercial

free development license

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, C++ (depending on the Berkeley DB edition)

C++

C and C++

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

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.

yes

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

all search fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

Splunk Search Processing Language for search commands

yes

APIs and other access methods

HTTP API

C++ API
Java API

HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Source-replica replication

yes

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual 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

authentication via encrypted signatures

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.