DBMS > Amazon Redshift vs. Microsoft Azure Cosmos DB vs. NSDb vs. TerminusDB vs. Yaacomo

System Properties Comparison Amazon Redshift vs. Microsoft Azure Cosmos DB vs. NSDb vs. TerminusDB vs. Yaacomo

Editorial information provided by DB-Engines

Name

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

Description

Large scale data warehouse service for use with business intelligence tools

Globally distributed, horizontally scalable, multi-model database service

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

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

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

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Graph DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
RDF store

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

Score	17.94
Rank	#34	Overall
	#21	Relational 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	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

aws.amazon.com/redshift

azure.microsoft.com/services/cosmos-db

nsdb.io

terminusdb.com

yaacomo.com

Technical documentation

docs.aws.amazon.com/redshift

learn.microsoft.com/azure/cosmos-db

nsdb.io/Architecture

terminusdb.github.io/terminusdb/#

Developer

Amazon (based on PostgreSQL)

Microsoft

DataChemist Ltd.

Q2WEB GmbH

Initial release

2012

2014

2017

2018

2009

Current release

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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

Java, Scala

Prolog, Rust

Server operating systems

hosted

Linux
macOS

Linux

Android
Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes: int, bigint, decimal, string

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.

Secondary indexes

restricted

yes

All properties auto-indexed by default

all fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

SQL-like query language (WOQL)

yes

APIs and other access methods

JDBC
ODBC

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

gRPC
HTTP REST
WebSocket

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

Java
Scala

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Python

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Graph Partitioning

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

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

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

in-memory journaling

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

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

Role-based access control

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.