DBMS > Microsoft Azure Cosmos DB vs. NuoDB vs. PostGIS vs. Tkrzw

System Properties Comparison Microsoft Azure Cosmos DB vs. NuoDB vs. PostGIS vs. Tkrzw

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

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Spatial extension of PostgreSQL

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Spatial DBMS

Key-value store

Secondary database models

Spatial DBMS

Relational DBMS

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

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

Score	0.87
Rank	#201	Overall
	#94	Relational DBMS

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

azure.microsoft.com/services/cosmos-db

www.3ds.com/nuodb-distributed-sql-database

postgis.net

dbmx.net/tkrzw

Technical documentation

learn.microsoft.com/azure/cosmos-db

doc.nuodb.com

postgis.net/documentation

Developer

Microsoft

Dassault Systèmes

originally NuoDB, Inc.

Mikio Hirabayashi

Initial release

2014

2013

2005

2020

Current release

3.4.2, February 2024

0.9.3, August 2020

License

Commercial or Open Source

commercial

limited edition free

Open Source

GPL v2.0

Open Source

Apache Version 2.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++

Server operating systems

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

Linux
macOS

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

Supported programming languages

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

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

JavaScript

Java, SQL

user defined functions

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

data is dynamically stored/cached on the nodes where it is read/written

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Managed transparently by NuoDB

yes

based on PostgreSQL

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

tunable commit protocol

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Temporary table

yes

using specific database classes

User concepts

Access control

Access rights can be defined down to the item level

Standard SQL roles/ privileges, Administrative Users

yes

based on PostgreSQL

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.