DBMS > Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. TerminusDB vs. UniData,UniVerse

System Properties Comparison Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. TerminusDB vs. UniData,UniVerse

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

A Wide Column Store for rapid development using massive semi-structured datasets

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Graph DBMS

Multivalue DBMS

Secondary database models

Spatial DBMS

Document store
RDF store

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	3.55
Rank	#80	Overall
	#6	Wide column stores

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Score	2.25
Rank	#112	Overall
	#2	Multivalue DBMS

Website

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

terminusdb.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

Technical documentation

learn.microsoft.com/azure/cosmos-db

terminusdb.github.io/terminusdb/#

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

Microsoft

DataChemist Ltd.

Rocket Software

Initial release

2014

2012

2018

1985

Current release

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

hosted

Linux

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

optional

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (WOQL)

yes

APIs and other access methods

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

RESTful HTTP API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

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

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

JavaScript
Python

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Graph Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Journaling Streams

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

optimistic locking

ACID

configurable

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

Access rights based on private key authentication or shared access signatures

Role-based access control

Access rights according to SQL-standard and operating system based

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.