DBMS > IBM Cloudant vs. Kingbase vs. MySQL vs. RisingWave

System Properties Comparison IBM Cloudant vs. Kingbase vs. MySQL vs. RisingWave

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

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

Widely used open source RDBMS

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

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	0.44
Rank	#258	Overall
	#117	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.61
Rank	#237	Overall
	#111	Relational DBMS

Website

www.ibm.com/products/cloudant

www.kingbase.com.cn

www.mysql.com

www.risingwave.com/database

Technical documentation

cloud.ibm.com/docs/Cloudant

dev.mysql.com/doc

docs.risingwave.com/docs/current/intro

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

BeiJing KINGBASE Information technologies inc.

Oracle

since 2010, originally MySQL AB, then Sun

RisingWave Labs

Initial release

2010

1999

1995

2022

Current release

V8.0, August 2021

9.0.0, July 2024

1.2, September 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 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

Erlang

C and Java

C and C++

Rust

Server operating systems

hosted

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

Standard SQL-types and JSON

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

Standard with numerous extensions

yes

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
PostgreSQL wire protocol

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

user defined functions

yes

proprietary syntax

UDFs in Python or Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

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

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

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

Users and 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.