DBMS > IBM Cloudant vs. Microsoft Azure Cosmos DB vs. TerminusDB vs. VoltDB

System Properties Comparison IBM Cloudant vs. Microsoft Azure Cosmos DB vs. TerminusDB vs. VoltDB

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
RDF store

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

Score	2.68
Rank	#106	Overall
	#20	Document stores

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

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

terminusdb.com

www.voltdb.com

Technical documentation

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

terminusdb.github.io/terminusdb/#

docs.voltdb.com

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

DataChemist Ltd.

VoltDB Inc.

Initial release

2010

2014

2018

2010

Current release

11.0.0, January 2023

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

GPL V3

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Prolog, Rust

Java, C++

Server operating systems

hosted

Linux

Linux
OS X

for development

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (WOQL)

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP/JSON API

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Java API
JDBC
RESTful HTTP/JSON API

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

JavaScript
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

JavaScript

yes

Java

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

Journaling Streams

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

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

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

in-memory journaling

yes

Snapshots and command logging

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

Role-based access control

Users and roles with access to stored procedures

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.