DBMS > Microsoft Azure Cosmos DB vs. PostGIS vs. SQLite vs. Yaacomo

System Properties Comparison Microsoft Azure Cosmos DB vs. PostGIS vs. SQLite vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Globally distributed, horizontally scalable, multi-model database service

Spatial extension of PostgreSQL

Widely used embeddable, in-process RDBMS

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Spatial DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Relational 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	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

azure.microsoft.com/services/cosmos-db

postgis.net

www.sqlite.org

yaacomo.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

postgis.net/documentation

www.sqlite.org/docs.html

Developer

Microsoft

Dwayne Richard Hipp

Q2WEB GmbH

Initial release

2014

2005

2000

2009

Current release

3.4.2, February 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

Open Source

Public Domain

commercial

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

Server operating systems

hosted

server-less

Android
Linux
Windows

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

yes

APIs and other access methods

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC

Supported programming languages

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

JavaScript

user defined functions

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

based on PostgreSQL

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

based on PostgreSQL

none

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

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

via file-system locks

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

yes

based on PostgreSQL

fine grained access rights according to SQL-standard

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.