DBMS > Immudb vs. Microsoft Azure Cosmos DB vs. OrigoDB vs. YDB

System Properties Comparison Immudb vs. Microsoft Azure Cosmos DB vs. OrigoDB vs. YDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Globally distributed, horizontally scalable, multi-model database service

A fully ACID in-memory object graph database

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Object oriented DBMS

Document store
Relational DBMS

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	0.31
Rank	#295	Overall
	#42	Key-value stores

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	0.33
Rank	#287	Overall
	#43	Document stores
	#132	Relational DBMS

Website

github.com/codenotary/immudb
immudb.io

azure.microsoft.com/services/cosmos-db

origodb.com

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

docs.immudb.io

learn.microsoft.com/azure/cosmos-db

origodb.com/docs

ydb.tech/en/docs

Developer

Codenotary

Microsoft

Robert Friberg et al

Yandex

Initial release

2020

2014

2009

under the name LiveDB

2019

Current release

1.2.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0; commercial license available

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

Server operating systems

BSD
Linux
macOS
Solaris
Windows
z/OS

hosted

Linux
Windows

Linux

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, 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 syntax

SQL-like query language

SQL-like query language (YQL)

APIs and other access methods

gRPC protocol
PostgreSQL wire protocol

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

.NET Client API
HTTP API
LINQ

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
Python

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

.Net

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Domain Events

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Source-replica replication

Active-passive shard 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

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

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

Access rights defined for Yandex Cloud users

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.