DBMS > Amazon DocumentDB vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. NuoDB vs. Tarantool

System Properties Comparison Amazon DocumentDB vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. NuoDB vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

NuoDB is a webscale distributed database that supports SQL and ACID transactions

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.89
Rank	#137	Overall
	#24	Document stores

Score	2.73
Rank	#108	Overall
	#20	Document stores

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

Score	0.99
Rank	#195	Overall
	#92	Relational DBMS

Score	1.67
Rank	#150	Overall
	#25	Document stores
	#25	Key-value stores
	#69	Relational DBMS

Website

aws.amazon.com/documentdb

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

www.3ds.com/nuodb-distributed-sql-database

www.tarantool.io

Technical documentation

aws.amazon.com/documentdb/resources

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

doc.nuodb.com

www.tarantool.io/en/doc

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Dassault Systèmes

originally NuoDB, Inc.

Initial release

2019

2010

2014

2013

2008

Current release

2.10.0, May 2022

License

Commercial or Open Source

commercial

limited edition free

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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++

C and C++

Server operating systems

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

BSD
Linux
macOS

Data scheme

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

JSON types

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

yes

Full-featured ANSI SQL support

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

RESTful HTTP/JSON API

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

ADO.NET
JDBC
ODBC

Open binary protocol

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

JavaScript

Java, SQL

Lua, C and SQL stored procedures

Triggers

yes

JavaScript

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

data is dynamically stored/cached on the nodes where it is read/written

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

yes

Managed transparently by NuoDB

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

ACID

tunable commit protocol

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

MVCC

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

Temporary table

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access rights for users and roles

Access rights for users can be defined per database

Access rights can be defined down to the item level

Standard SQL roles/ privileges, Administrative Users

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.