DBMS > atoti vs. Microsoft Azure Cosmos DB vs. Newts vs. PostGIS vs. Postgres-XL

System Properties Comparison atoti vs. Microsoft Azure Cosmos DB vs. Newts vs. PostGIS vs. Postgres-XL

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

Globally distributed, horizontally scalable, multi-model database service

Time Series DBMS based on Cassandra

Spatial extension of PostgreSQL

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

Primary database model

Object oriented DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Relational DBMS

Document store
Spatial DBMS

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

Score	0.56
Rank	#245	Overall
	#10	Object oriented DBMS

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

atoti.io

azure.microsoft.com/services/cosmos-db

opennms.github.io/newts

postgis.net

www.postgres-xl.org

Technical documentation

docs.atoti.io

learn.microsoft.com/azure/cosmos-db

github.com/OpenNMS/newts/wiki

postgis.net/documentation

www.postgres-xl.org/documentation

Developer

ActiveViam

Microsoft

OpenNMS Group

Initial release

2014

2005

2014

since 2012, originally named StormDB

Current release

3.4.2, February 2024

10 R1, October 2018

License

Commercial or Open Source

commercial

free versions available

commercial

Open Source

Apache 2.0

Open Source

GPL v2.0

Open Source

Mozilla public license

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

Java

Server operating systems

hosted

Linux
OS X
Windows

Linux
macOS

Data scheme

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

Multidimensional Expressions (MDX)

SQL-like query language

yes

distributed, parallel query execution

APIs and other access methods

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

HTTP REST
Java API

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

Supported programming languages

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

Java

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

Server-side scripts

Stored procedures

Python

JavaScript

user defined functions

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

Sharding

Implicit feature of the cloud service

Sharding

based on Cassandra

yes

based on PostgreSQL

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

selectable replication factor

based on Cassandra

yes

based on PostgreSQL

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

MVCC

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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.