DBMS > IBM Cloudant vs. IBM Db2 warehouse vs. Microsoft Azure Cosmos DB vs. TinkerGraph

System Properties Comparison IBM Cloudant vs. IBM Db2 warehouse vs. Microsoft Azure Cosmos DB vs. TinkerGraph

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

Cloud-based data warehousing service

Globally distributed, horizontally scalable, multi-model database service

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Secondary database models

Spatial DBMS

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

Score	2.73
Rank	#108	Overall
	#20	Document stores

Score	1.34
Rank	#166	Overall
	#76	Relational DBMS

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

Score	0.12
Rank	#344	Overall
	#34	Graph DBMS

Website

www.ibm.com/products/cloudant

www.ibm.com/products/db2/warehouse

azure.microsoft.com/services/cosmos-db

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

IBM

Microsoft

Initial release

2010

2014

2009

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

Java

Server operating systems

hosted

Data scheme

schema-free

yes

schema-free

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.

Import/export of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
OLE DB

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

TinkerPop 3

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

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

Groovy
Java

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

PL/SQL, SQL PL

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

atomic operations within a document possible

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

optional

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 can be defined per database

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.