DBMS > IBM Cloudant vs. KairosDB vs. Microsoft Azure Cosmos DB vs. Teradata

System Properties Comparison IBM Cloudant vs. KairosDB vs. Microsoft Azure Cosmos DB vs. Teradata

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

Distributed Time Series DBMS based on Cassandra or H2

Globally distributed, horizontally scalable, multi-model database service

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Document store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.85
Rank	#95	Overall
	#18	Document stores

Score	0.60
Rank	#238	Overall
	#20	Time Series DBMS

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

Score	41.47
Rank	#22	Overall
	#15	Relational DBMS

Website

www.ibm.com/products/cloudant

github.com/kairosdb/kairosdb

azure.microsoft.com/services/cosmos-db

www.teradata.com

Technical documentation

cloud.ibm.com/docs/Cloudant

kairosdb.github.io

learn.microsoft.com/azure/cosmos-db

docs.teradata.com

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Teradata

Initial release

2010

2013

2014

1984

Current release

1.2.2, November 2018

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

Java

Server operating systems

hosted

Linux
OS X
Windows

hosted

hosted
Linux

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

SQL-like query language

yes

SQL 2016 + extensions

APIs and other access methods

RESTful HTTP/JSON API

Graphite protocol
HTTP REST
Telnet API

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

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

Java
JavaScript

Node.js
PHP
Python

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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

JavaScript

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

Implicit feature of the cloud service

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

based on Cassandra

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

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

based on Cassandra
Immediate Consistency

based on Cassandra

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate 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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

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.

yes

User concepts

Access control

Access rights for users can be defined per database

simple password-based access control

Access rights can be defined down to the item level

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.