DBMS > Microsoft Azure Cosmos DB vs. OrigoDB vs. TigerGraph vs. Yanza

System Properties Comparison Microsoft Azure Cosmos DB vs. OrigoDB vs. TigerGraph vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Globally distributed, horizontally scalable, multi-model database service

A fully ACID in-memory object graph database

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Time Series DBMS for IoT Applications

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Object oriented DBMS

Graph DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

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

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

azure.microsoft.com/services/cosmos-db

origodb.com

www.tigergraph.com

yanza.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

origodb.com/docs

docs.tigergraph.com

Developer

Microsoft

Robert Friberg et al

Yanza

Initial release

2014

2009

under the name LiveDB

2017

2015

License

Commercial or Open Source

commercial

Open Source

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

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

Linux
Windows

Linux

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (GSQL)

APIs and other access methods

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

.NET Client API
HTTP API
LINQ

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

HTTP API

Supported programming languages

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

.Net

C++
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Domain Events

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

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

depending on model

yes

Relationships in graphs

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

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

Role-based access control

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.