DBMS > IBM Cloudant vs. Microsoft Azure Cosmos DB vs. RavenDB vs. SWC-DB vs. Transbase

System Properties Comparison IBM Cloudant vs. Microsoft Azure Cosmos DB vs. RavenDB vs. SWC-DB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Open Source Operational and Transactional Enterprise NoSQL Document Database

A high performance, scalable Wide Column DBMS

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

Time Series DBMS

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

Score	2.73
Rank	#108	Overall
	#20	Document stores

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

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.01
Rank	#387	Overall
	#13	Wide column stores

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

ravendb.net

github.com/kashirin-alex/swc-db
www.swcdb.org

www.transaction.de/en/products/transbase.html

Technical documentation

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

ravendb.net/docs

www.transaction.de/en/products/transbase/features.html

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Hibernating Rhinos

Alex Kashirin

Transaction Software GmbH

Initial release

2010

2014

2010

2020

1987

Current release

5.4, July 2022

0.5, April 2021

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

GPL V3

commercial

free development license

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

C++

C and C++

Server operating systems

hosted

Linux
macOS
Raspberry Pi
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (RQL)

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

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

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

Proprietary protocol
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

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

C++

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

Multi-source replication

Source-replica 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

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.

Immediate Consistency

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, Cluster-wide transaction available

yes

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

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

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.