DBMS > Microsoft Azure Cosmos DB vs. Microsoft Azure SQL Database vs. searchxml vs. SwayDB

System Properties Comparison Microsoft Azure Cosmos DB vs. Microsoft Azure SQL Database vs. searchxml vs. SwayDB

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

DBMS for structured and unstructured content wrapped with an application server

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Native XML DBMS
Search engine

Key-value 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	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

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

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

azure.microsoft.com/services/cosmos-db

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

www.searchxml.net/category/products

swaydb.simer.au

Technical documentation

learn.microsoft.com/azure/cosmos-db

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

www.searchxml.net/support/handouts

Developer

Microsoft

informationpartners gmbh

Simer Plaha

Initial release

2014

2010

2015

2018

Current release

V12

1.0

License

Commercial or Open Source

commercial

Open Source

GNU Affero GPL V3.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

C++

Scala

Server operating systems

hosted

Windows

Data scheme

schema-free

yes

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

RESTful HTTP API
WebDAV
XQuery
XSLT

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

C++

most other programming languages supported via APIs

Java
Kotlin
Scala

Server-side scripts

Stored procedures

JavaScript

Transact SQL

yes

on the application server

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes, with always 3 replicas available

yes

sychronisation to multiple collections

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

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

multiple readers, single writer

Atomic execution of operations

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

User concepts

Access control

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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

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.