DBMS > Amazon DynamoDB vs. BoltDB vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. NSDb

System Properties Comparison Amazon DynamoDB vs. BoltDB vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. NSDb

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

An embedded key-value store for Go.

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Primary database model

Document store
Key-value store

Key-value store

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	0.76
Rank	#224	Overall
	#32	Key-value 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.00
Rank	#396	Overall
	#42	Time Series DBMS

Website

aws.amazon.com/dynamodb

github.com/boltdb/bolt

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

nsdb.io

Technical documentation

docs.aws.amazon.com/dynamodb

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

nsdb.io/Architecture

Developer

Amazon

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Initial release

2012

2013

2010

2014

2017

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

MIT License

commercial

Open Source

Apache Version 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, Scala

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

hosted

Linux
macOS

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

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

gRPC
HTTP REST
WebSocket

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Java
Scala

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

JavaScript

Triggers

yes

by integration with AWS Lambda

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

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

Eventual Consistency
Immediate Consistency

can be specified for read operations

none

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

yes

atomic operations within a document possible

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

Using Apache Lucene

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 and roles can be defined via the AWS Identity and Access Management (IAM)

Access rights for users can be defined per database

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.