DBMS > Microsoft Azure Cosmos DB vs. PostGIS vs. RethinkDB vs. Yanza

System Properties Comparison Microsoft Azure Cosmos DB vs. PostGIS vs. RethinkDB vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Globally distributed, horizontally scalable, multi-model database service

Spatial extension of PostgreSQL

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Time Series DBMS for IoT Applications

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Spatial DBMS

Document store

Time Series DBMS

Secondary database models

Spatial DBMS

Relational 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	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	2.74
Rank	#105	Overall
	#19	Document stores

Website

azure.microsoft.com/services/cosmos-db

postgis.net

rethinkdb.com

yanza.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

postgis.net/documentation

rethinkdb.com/docs

Developer

Microsoft

The Linux Foundation

since July 2017

Yanza

Initial release

2014

2005

2009

2015

Current release

3.4.2, February 2024

2.4.1, August 2020

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

Open Source

Apache Version 2

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

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

Linux
OS X
Windows

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

string, binary, float, bool, date, geometry

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

HTTP API

Supported programming languages

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

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

any language that supports HTTP calls

Server-side scripts

Stored procedures

JavaScript

user defined functions

Triggers

JavaScript

yes

Client-side triggers through changefeeds

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

based on PostgreSQL

Sharding

range based

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

based on PostgreSQL

Source-replica replication

none

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

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

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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

yes

based on PostgreSQL

yes

users and table-level permissions

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.