DBMS > Immudb vs. Microsoft Azure Cosmos DB vs. Riak KV vs. STSdb

System Properties Comparison Immudb vs. Microsoft Azure Cosmos DB vs. Riak KV vs. STSdb

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

Distributed, fault tolerant key-value store

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Key-value store

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	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

github.com/codenotary/immudb
immudb.io

azure.microsoft.com/services/cosmos-db

github.com/STSSoft/STSdb4

Technical documentation

docs.immudb.io

learn.microsoft.com/azure/cosmos-db

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Codenotary

Microsoft

OpenSource, formerly Basho Technologies

STS Soft SC

Initial release

2020

2014

2009

2011

Current release

1.2.3, April 2022

3.2.0, December 2022

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPLv2, 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

Erlang

Server operating systems

BSD
Linux
macOS
Solaris
Windows
z/OS

hosted

Linux
OS X

Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

primitive types and user defined types (classes)

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

restricted

SQL

Support of SQL

SQL-like syntax

SQL-like query language

APIs and other access methods

gRPC protocol
PostgreSQL wire protocol

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

HTTP API
Native Erlang Interface

.NET Client API

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C#
Java

Server-side scripts

Stored procedures

JavaScript

Erlang

Triggers

JavaScript

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

selectable replication factor

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

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

Access rights can be defined down to the item level

yes, using Riak Security

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.