DBMS > IBM Cloudant vs. Microsoft Azure Cosmos DB vs. Splunk vs. Transwarp ArgoDB

System Properties Comparison IBM Cloudant vs. Microsoft Azure Cosmos DB vs. Splunk vs. Transwarp ArgoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Analytics Platform for Big Data

Distributed Analytical Database to replace Hadoop+MPP hybrid architecture

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Search engine

Relational DBMS

Secondary database models

Spatial DBMS

Search engine

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	0.12
Rank	#348	Overall
	#151	Relational DBMS

Website

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

www.splunk.com

www.transwarp.cn/en/product/argodb

Technical documentation

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

docs.splunk.com/Documentation/Splunk

docs.transwarp.cn/#/documents-support/docs?category=ARGODB

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Splunk Inc.

Transwarp

Initial release

2010

2014

2003

License

Commercial or Open Source

commercial

Limited free edition and free developer edition available

commercial

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

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

Splunk Search Processing Language for search commands

yes

APIs and other access methods

RESTful HTTP/JSON API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

HTTP REST

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

JavaScript

yes

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

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

In-memory capabilities

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

User concepts

Access control

Access rights for users can be defined per database

Access rights can be defined down to the item level

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.