DBMS > IBM Cloudant vs. Microsoft Azure Cosmos DB vs. ObjectBox vs. ToroDB

System Properties Comparison IBM Cloudant vs. Microsoft Azure Cosmos DB vs. ObjectBox vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Lightweight, fast on-device database for IoT, Mobile and Embedded devices, persisting and synchronising objects and vectors

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Object oriented DBMS
Vector DBMS

Document store

Secondary database models

Spatial DBMS

Time Series DBMS

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

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

Score	1.29
Rank	#166	Overall
	#5	Object oriented DBMS
	#7	Vector DBMS

Website

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

github.com/objectbox
objectbox.io

github.com/torodb/server

Technical documentation

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

docs.objectbox.io

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

ObjectBox Limited

8Kdata

Initial release

2010

2014

2017

2016

Current release

4.0 (May 2024)

License

Commercial or Open Source

commercial

Bindings are released under Apache 2.0

Apache License 2.0

Open Source

AGPL-V3

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 and C++

Java

Server operating systems

hosted

Android
Any POSIX system
Docker
iOS
Linux
macOS
QNX
Windows

All OS with a Java 7 VM

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes, plus "flex" map-like types

yes

string, integer, double, boolean, date, object_id

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

APIs and other access methods

RESTful HTTP/JSON API

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

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

C
C++
Dart (Flutter)
Go
Java
Kotlin
Python
Swift

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

Data sync between devices allowing occasional connected databases to work completely offline

Source-replica replication

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

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Eventual Consistency
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

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

yes

Access rights for users and roles

More information provided by the system vendor

News

The on-device Vector Database for Android and Java
29 May 2024

Vector search: making sense of search queries
29 May 2024

Python on-device Vector and Object Database for Local AI
28 May 2024

Evolution of search: traditional vs vector search
23 May 2024

On-device Vector Database for Dart/Flutter
21 May 2024

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.