DBMS > BaseX vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. Prometheus

System Properties Comparison BaseX vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. Prometheus

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Open-source Time Series DBMS and monitoring system

Primary database model

Native XML DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	1.73
Rank	#142	Overall
	#4	Native XML 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	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

basex.org

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

prometheus.io

Technical documentation

docs.basex.org

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

prometheus.io/docs

Developer

BaseX GmbH

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Initial release

2007

2010

2014

2015

Current release

10.7, August 2023

License

Commercial or Open Source

Open Source

BSD license

commercial

Open Source

Apache 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

Server operating systems

Linux
OS X
Windows

hosted

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

XQuery supports types

yes

JSON types

Numeric data only

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.

Import of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

RESTful HTTP/JSON API

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

RESTful HTTP/JSON API

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

yes

View functions (Map-Reduce) in JavaScript

JavaScript

Triggers

yes

via events

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

yes

by Federation

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

none

Foreign keys

Referential integrity

Transaction concepts

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

multiple readers, single writer

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.

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

Access rights for users can be defined per database

Access rights can be defined down to the item level

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.