DBMS > Amazon DocumentDB vs. Microsoft Azure Cosmos DB vs. PlanetScale vs. STSdb

System Properties Comparison Amazon DocumentDB vs. Microsoft Azure Cosmos DB vs. PlanetScale vs. STSdb

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

Globally distributed, horizontally scalable, multi-model database service

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	1.91
Rank	#124	Overall
	#22	Document stores

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

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Website

aws.amazon.com/documentdb

azure.microsoft.com/services/cosmos-db

planetscale.com

github.com/STSSoft/STSdb4

Technical documentation

aws.amazon.com/documentdb/resources

learn.microsoft.com/azure/cosmos-db

planetscale.com/docs

Developer

Microsoft

PlanetScale

STS Soft SC

Initial release

2019

2014

2020

2011

Current release

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

GPLv2, commercial license available

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

Server operating systems

hosted

Docker
Linux
macOS

Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

primitive types and user defined types (classes)

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

with proprietary extensions

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

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

ADO.NET
JDBC
MySQL protocol
ODBC

.NET Client API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
Java

Server-side scripts

Stored procedures

JavaScript

yes

proprietary syntax

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-document operations

Multi-item ACID transactions with snapshot isolation within a partition

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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.

yes

User concepts

Access control

Access rights for users and roles

Access rights can be defined down to the item level

Users with fine-grained authorization concept

no user groups or 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.