DBMS > EventStoreDB vs. IBM Cloudant vs. IBM Db2 vs. MySQL

System Properties Comparison EventStoreDB vs. IBM Cloudant vs. IBM Db2 vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Database as a Service offering based on Apache CouchDB

Common in IBM host environments, 2 different versions for host and Windows/Linux

Widely used open source RDBMS

Primary database model

Event Store

Document store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Document store
Spatial DBMS

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

Score	1.07
Rank	#181	Overall
	#1	Event Stores

Score	2.85
Rank	#95	Overall
	#18	Document stores

Score	123.05
Rank	#9	Overall
	#6	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

www.eventstore.com

www.ibm.com/products/cloudant

www.ibm.com/products/db2

www.mysql.com

Technical documentation

developers.eventstore.com

cloud.ibm.com/docs/Cloudant

www.ibm.com/docs/en/db2

dev.mysql.com/doc

Developer

Event Store Limited

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

IBM

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2010

1983

host version

1995

Current release

21.2, February 2021

12.1, October 2016

9.0.0, July 2024

License

Commercial or Open Source

Open Source

commercial

free version is available

Open Source

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

C and C++

Server operating systems

Linux
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

with proprietary extensions

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

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

with separate tools (MQ, InfoSphere)

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

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.