DBMS > Microsoft Azure Cosmos DB vs. Microsoft Azure SQL Database vs. OpenQM vs. Percona Server for MongoDB

System Properties Comparison Microsoft Azure Cosmos DB vs. Microsoft Azure SQL Database vs. OpenQM vs. Percona Server for MongoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Globally distributed, horizontally scalable, multi-model database service

Database as a Service offering with high compatibility to Microsoft SQL Server

QpenQM is a high-performance, self-tuning, multi-value DBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Multivalue DBMS

Document store

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

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

Score	72.95
Rank	#16	Overall
	#11	Relational DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Score	0.50
Rank	#250	Overall
	#39	Document stores

Website

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/products/azure-sql/database

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

learn.microsoft.com/azure/cosmos-db

docs.microsoft.com/en-us/azure/azure-sql

docs.percona.com/percona-distribution-for-mongodb

Developer

Microsoft

Rocket Software, originally Martin Phillips

Percona

Initial release

2014

2010

1993

2015

Current release

V12

3.4-12

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

Open Source

GPL Version 2

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

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux

Data scheme

schema-free

yes

with some exceptions

schema-free

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC

proprietary protocol using JSON

Supported programming languages

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

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

.Net
Basic
C
Java
Objective C
PHP
Python

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

JavaScript

Transact SQL

yes

JavaScript

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes, with always 3 replicas available

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

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.

yes

via In-Memory Engine

User concepts

Access control

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

Access rights for users and 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.