DBMS > Microsoft Azure Cosmos DB vs. Postgres-XL vs. SwayDB vs. VoltDB

System Properties Comparison Microsoft Azure Cosmos DB vs. Postgres-XL vs. SwayDB vs. VoltDB

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

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

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

azure.microsoft.com/services/cosmos-db

www.postgres-xl.org

swaydb.simer.au

www.voltdb.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

www.postgres-xl.org/documentation

docs.voltdb.com

Developer

Microsoft

Simer Plaha

VoltDB Inc.

Initial release

2014

since 2012, originally named StormDB

2018

2010

Current release

10 R1, October 2018

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Mozilla public license

Open Source

GNU Affero GPL V3.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Scala

Java, C++

Server operating systems

hosted

Linux
macOS

Linux
OS X

for development

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.

yes

XML type, but no XML query functionality

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

distributed, parallel query execution

yes

only a subset of SQL 99

APIs and other access methods

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Java
Kotlin
Scala

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

JavaScript

user defined functions

Java

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

MVCC

Atomic execution of operations

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

Users and roles with access to stored procedures

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.