DBMS > IBM Cloudant vs. MonetDB vs. MySQL vs. RavenDB vs. Ultipa

System Properties Comparison IBM Cloudant vs. MonetDB vs. MySQL vs. RavenDB vs. Ultipa

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

A relational database management system that stores data in columns

Widely used open source RDBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

High performance Graph DBMS supporting HTAP high availability cluster deployment

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Document store

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.13
Rank	#335	Overall
	#31	Graph DBMS

Website

www.ibm.com/products/cloudant

Technical documentation

cloud.ibm.com/docs/Cloudant

www.monetdb.org/Documentation

dev.mysql.com/doc

ravendb.net/docs

www.ultipa.com/document

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

MonetDB BV

Oracle

since 2010, originally MySQL AB, then Sun

Hibernating Rhinos

Ultipa

Initial release

2010

2004

1995

2010

2019

Current release

Dec2023 (11.49), December 2023

8.4.0, April 2024

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

Mozilla Public License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL version 3, commercial license available

commercial

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Erlang

C and C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

SQL 2003 with some extensions

yes

with proprietary extensions

SQL-like query language (RQL)

APIs and other access methods

RESTful HTTP/JSON API

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

ADO.NET
JDBC
ODBC
Proprietary native 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

RESTful HTTP API

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

C++
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes, in SQL, C, R

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding via remote tables

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication available in experimental status

Multi-source replication
Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual 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

not for MyISAM storage engine

Transaction concepts

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

atomic operations within a document possible

ACID

not for MyISAM storage engine

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.