DBMS > IBM Cloudant vs. Lovefield vs. OpenTSDB vs. RocksDB vs. Splunk

System Properties Comparison IBM Cloudant vs. Lovefield vs. OpenTSDB vs. RocksDB vs. Splunk

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Embeddable relational database for web apps written in pure JavaScript

Scalable Time Series DBMS based on HBase

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

Analytics Platform for Big Data

Primary database model

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

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

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

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

www.ibm.com/products/cloudant

google.github.io/lovefield

opentsdb.net

rocksdb.org

www.splunk.com

Technical documentation

cloud.ibm.com/docs/Cloudant

github.com/google/lovefield/blob/master/docs/spec_index.md

opentsdb.net/docs/build/html/index.html

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Google

currently maintained by Yahoo and other contributors

Facebook, Inc.

Splunk Inc.

Initial release

2010

2014

2011

2013

2003

Current release

2.1.12, February 2017

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

LGPL

Open Source

BSD

commercial

Limited free edition and free developer edition available

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

Erlang

JavaScript

Java

C++

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
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

numeric data for metrics, strings for tags

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

SQL-like query language

via JavaScript builder pattern

Splunk Search Processing Language for search commands

APIs and other access methods

RESTful HTTP/JSON API

HTTP API
Telnet API

C++ API
Java API

HTTP REST

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript

Erlang
Go
Java
Python
R
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

Triggers

yes

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

selectable replication factor

based on HBase

yes

Multi-source 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

based on HBase

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

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

Optimistic locking

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

yes

User concepts

Access control

Access rights for users can be defined per database

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.