DBMS > Amazon DocumentDB vs. Google Cloud Spanner vs. Microsoft Azure Cosmos DB vs. SpaceTime

System Properties Comparison Amazon DocumentDB vs. Google Cloud Spanner vs. Microsoft Azure Cosmos DB vs. SpaceTime

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

Globally distributed, horizontally scalable, multi-model database service

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Spatial DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	2.89
Rank	#103	Overall
	#52	Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

aws.amazon.com/documentdb

cloud.google.com/spanner

azure.microsoft.com/services/cosmos-db

www.mireo.com/spacetime

Technical documentation

aws.amazon.com/documentdb/resources

cloud.google.com/spanner/docs

learn.microsoft.com/azure/cosmos-db

Developer

Google

Microsoft

Mireo

Initial release

2019

2017

2014

2020

License

Commercial or Open Source

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

C++

Server operating systems

hosted

Linux

Data scheme

schema-free

yes

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

SQL

Support of SQL

yes

Query statements complying to ANSI 2011

SQL-like query language

A subset of ANSI SQL is implemented

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

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

RESTful HTTP API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

Go
Java
JavaScript (Node.js)
Python

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

C#
C++
Python

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Fixed-grid hypercubes

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 with 3 replicas for regional instances.

yes

Implicit feature of the cloud service

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

Atomic single-document operations

ACID

Strict serializable isolation

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

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

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

yes

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.