DBMS > Amazon DocumentDB vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. searchxml vs. Sequoiadb

System Properties Comparison Amazon DocumentDB vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. searchxml vs. Sequoiadb

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

A Wide Column Store for rapid development using massive semi-structured datasets

DBMS for structured and unstructured content wrapped with an application server

NewSQL database with distributed OLTP and SQL

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Native XML DBMS
Search engine

Document store
Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

aws.amazon.com/documentdb

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

www.searchxml.net/category/products

www.sequoiadb.com

Technical documentation

aws.amazon.com/documentdb/resources

learn.microsoft.com/azure/cosmos-db

www.searchxml.net/support/handouts

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Microsoft

informationpartners gmbh

Sequoiadb Ltd.

Initial release

2019

2014

2012

2015

2013

Current release

1.0

License

Commercial or Open Source

commercial

Open Source

Server: AGPL; Client: Apache V2

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

Windows

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

oid, date, timestamp, binary, regex

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

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

RESTful HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

proprietary protocol using JSON

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

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

C++

most other programming languages supported via APIs

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

JavaScript

yes

on the application server

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

none

Sharding

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

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

sychronisation to multiple collections

Source-replica replication

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

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

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

optimistic locking

multiple readers, single writer

Document is locked during a transaction

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 can be defined down to the item level

Access rights based on private key authentication or shared access signatures

Domain, group and role-based access control at the document level and for application services

simple password-based access control

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.