DBMS > IBM Cloudant vs. MySQL vs. TDSQL for MySQL vs. Transwarp Hippo

System Properties Comparison IBM Cloudant vs. MySQL vs. TDSQL for MySQL vs. Transwarp Hippo

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

Widely used open source RDBMS

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

Cloud-native distributed Vector DBMS that supports storage, retrieval, and management of massive vector-based datasets

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Vector DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.85
Rank	#205	Overall
	#95	Relational DBMS

Score	0.00
Rank	#383	Overall
	#13	Vector DBMS

Website

www.ibm.com/products/cloudant

www.mysql.com

www.tencentcloud.com/products/dcdb

www.transwarp.cn/en/subproduct/hippo

Technical documentation

cloud.ibm.com/docs/Cloudant

dev.mysql.com/doc

www.tencentcloud.com/document/product/1042

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle

since 2010, originally MySQL AB, then Sun

Tencent

Initial release

2010

1995

2013

2023

Current release

8.4.0, April 2024

1.0, May 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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++

C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

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

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

RESTful HTTP API

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

C
C#
C++
Java
PHP
Python
Ruby

C++
Java
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

Immediate Consistency

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

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

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept

Role based access control and fine grained access rights

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.