DBMS > IBM Cloudant vs. mSQL vs. OrigoDB vs. Vitess

System Properties Comparison IBM Cloudant vs. mSQL vs. OrigoDB vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.85
Rank	#95	Overall
	#18	Document stores

Score	1.26
Rank	#163	Overall
	#74	Relational DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

www.ibm.com/products/cloudant

hughestech.com.au/products/msql

origodb.com

vitess.io

Technical documentation

cloud.ibm.com/docs/Cloudant

origodb.com/docs

vitess.io/docs

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Hughes Technologies

Robert Friberg et al

The Linux Foundation, PlanetScale

Initial release

2010

1994

2009

under the name LiveDB

2013

Current release

4.4, October 2021

15.0.2, December 2022

License

Commercial or Open Source

commercial

free licenses can be provided

Open Source

Apache Version 2.0, commercial licenses 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

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

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

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

proprietary syntax

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

none

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

depending on model

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

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

Users with fine-grained authorization concept

no user groups or roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, IBM

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, IBM

From Cloud Foundry to Code Engine: Service Bindings and Code
15 March 2022, IBM

provided by Google News

Deepthi Sigireddi on Distributed Database Architecture in the Cloud Native Era
20 May 2024, InfoQ.com

They scaled YouTube — now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale offers undo button to reverse schema migration without losing data
24 March 2022, The Register

3 Cloud-Native Database Tools From CNCF
26 July 2022, Cloud Native Now

provided by Google News

Share this page