DBMS > chDB vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. OpenEdge vs. RavenDB

System Properties Comparison chDB vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. OpenEdge vs. RavenDB

Editorial information provided by DB-Engines

Name

Description

An embedded SQL OLAP Engine powered by ClickHouse

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Application development environment with integrated database management system

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Document store

Secondary database models

Time Series DBMS

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

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

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

github.com/chdb-io/chdb

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

www.progress.com/openedge

ravendb.net

Technical documentation

doc.chdb.io

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

documentation.progress.com/output/ua/OpenEdge_latest

ravendb.net/docs

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Progress Software Corporation

Hibernating Rhinos

Initial release

2023

2010

2014

1984

2010

Current release

OpenEdge 12.2, March 2020

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

AGPL version 3, 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

server-less

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language

yes

close to SQL 92

SQL-like query language (RQL)

APIs and other access methods

RESTful HTTP/JSON API

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

JDBC
ODBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

Bun
C
C++
Go
JavaScript (Node.js)
Python
Rust

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Progress proprietary ABL (Advanced Business Language)

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

JavaScript

yes

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

since Version 11.4

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

ACID

ACID, Cluster-wide transaction available

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.

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 groups

Authorization levels configured per client per database

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.