DBMS > IBM Cloudant vs. IBM Db2 vs. IRONdb vs. Microsoft Azure Cosmos DB

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Database as a Service offering based on Apache CouchDB

Common in IBM host environments, 2 different versions for host and Windows/Linux

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Spatial DBMS

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

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

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

Website

www.ibm.com/products/cloudant

www.ibm.com/products/db2

www.circonus.com/solutions/time-series-database/

azure.microsoft.com/services/cosmos-db

Technical documentation

cloud.ibm.com/docs/Cloudant

www.ibm.com/docs/en/db2

docs.circonus.com/irondb/category/getting-started

learn.microsoft.com/azure/cosmos-db

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

IBM

Circonus LLC.

Microsoft

Initial release

2010

1983

host version

2017

2014

Current release

12.1, October 2016

V0.10.20, January 2018

License

Commercial or Open Source

commercial

free version is 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

C and C++

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

HTTP API

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

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

yes, in Lua

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

with separate tools (MQ, InfoSphere)

configurable replication factor, datacenter aware

yes

Implicit feature of the cloud service

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 per node, eventual consistency across nodes

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

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

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

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.