DBMS > ArcadeDB vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. RisingWave

System Properties Comparison ArcadeDB vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. RisingWave

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Document store

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	0.02
Rank	#374	Overall
	#52	Document stores
	#38	Graph DBMS
	#56	Key-value stores
	#38	Time Series DBMS

Score	2.85
Rank	#95	Overall
	#18	Document stores

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

Score	0.61
Rank	#237	Overall
	#111	Relational DBMS

Website

arcadedb.com

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

www.risingwave.com/database

Technical documentation

docs.arcadedb.com

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

docs.risingwave.com/docs/current/intro

Developer

Arcade Data

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

RisingWave Labs

Initial release

2021

2010

2014

2022

Current release

September 2021

1.2, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

Erlang

Rust

Server operating systems

All OS with a Java VM

hosted

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language, no joins

SQL-like query language

yes

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

RESTful HTTP/JSON API

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

JDBC
PostgreSQL wire protocol

Supported programming languages

Java

C#
Java
JavaScript
Objective-C
PHP
Ruby

.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

View functions (Map-Reduce) in JavaScript

JavaScript

UDFs in Python or Java

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

Transaction concepts

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

ACID

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users can be defined per database

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.