DBMS > Amazon SimpleDB vs. BigchainDB vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. NSDb

System Properties Comparison Amazon SimpleDB vs. BigchainDB vs. Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. NSDb

Editorial information provided by DB-Engines

Name

Description

Hosted simple database service by Amazon, with the data stored in the Amazon Cloud.

There is an unrelated product called SimpleDB developed by Edward Sciore

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

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	1.88
Rank	#133	Overall
	#23	Key-value stores

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

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

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Website

aws.amazon.com/simpledb

www.bigchaindb.com

cloud.google.com/datastore

azure.microsoft.com/services/cosmos-db

nsdb.io

Technical documentation

docs.aws.amazon.com/simpledb

bigchaindb.readthedocs.io/en/latest

cloud.google.com/datastore/docs

learn.microsoft.com/azure/cosmos-db

nsdb.io/Architecture

Developer

Amazon

Google

Microsoft

Initial release

2007

2016

2008

2014

2017

License

Commercial or Open Source

commercial

Open Source

AGPL v3

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

Python

Java, Scala

Server operating systems

hosted

Linux

hosted

Linux
macOS

Data scheme

schema-free

Typing

predefined data types such as float or date

yes, details here

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 columns are indexed automatically

yes

All properties auto-indexed by default

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

APIs and other access methods

RESTful HTTP API

CLI Client
RESTful HTTP API

gRPC (using protocol buffers) 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
C
C++
Erlang
Java
PHP
Python
Ruby
Scala

Go
Haskell
Java
JavaScript
Python
Ruby

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

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

Java
Scala

Server-side scripts

Stored procedures

using Google App Engine

JavaScript

Triggers

Callbacks using the Google Apps Engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding must be implemented in the application

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication using Paxos

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

Concurrent data updates can be detected by the application

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

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)

yes

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.