DBMS > Atos Standard Common Repository vs. IRONdb vs. Microsoft Azure Cosmos DB vs. RisingWave

System Properties Comparison Atos Standard Common Repository vs. IRONdb vs. Microsoft Azure Cosmos DB vs. RisingWave

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

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

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Globally distributed, horizontally scalable, multi-model database service

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

Primary database model

Document store
Key-value store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational 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.64
Rank	#238	Overall
	#110	Relational DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.circonus.com/solutions/time-series-database/

azure.microsoft.com/services/cosmos-db

www.risingwave.com/database

Technical documentation

docs.circonus.com/irondb/category/getting-started

learn.microsoft.com/azure/cosmos-db

docs.risingwave.com/docs/current/intro

Developer

Atos Convergence Creators

Circonus LLC.

Microsoft

RisingWave Labs

Initial release

2016

2017

2014

2022

Current release

1703

V0.10.20, January 2018

1.2, September 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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

C and C++

Rust

Server operating systems

Linux

hosted

Docker
Linux
macOS

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

text, numeric, histograms

yes

JSON types

Standard SQL-types and JSON

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like query language

yes

APIs and other access methods

LDAP

HTTP API

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

JDBC
PostgreSQL wire protocol

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes, in Lua

JavaScript

UDFs in Python or Java

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

yes

Implicit feature of the cloud service

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 or Eventual Consistency depending on configuration

Immediate consistency per node, eventual consistency across nodes

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

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.

yes

User concepts

Access control

LDAP bind authentication

Access rights can be defined down to the item level

Users and Roles

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.