DBMS > IBM Db2 vs. IBM Db2 Event Store vs. MySQL vs. Prometheus

System Properties Comparison IBM Db2 vs. IBM Db2 Event Store vs. MySQL vs. Prometheus

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Distributed Event Store optimized for Internet of Things use cases

Widely used open source RDBMS

Open-source Time Series DBMS and monitoring system

Primary database model

Relational DBMS

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

Event Store
Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

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	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Website

www.ibm.com/products/db2

www.ibm.com/products/db2-event-store

www.mysql.com

prometheus.io

Technical documentation

www.ibm.com/docs/en/db2

www.ibm.com/docs/en/db2-event-store

dev.mysql.com/doc

prometheus.io/docs

Developer

IBM

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

1983

host version

2017

1995

2015

Current release

12.1, October 2016

2.0

8.4.0, April 2024

License

Commercial or Open Source

commercial

free version is available

commercial

free developer edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

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

C and C++

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux

Linux, macOS, Windows for the developer addition

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP/JSON API

Supported programming languages

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

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

Active-active shard replication

Multi-source replication
Source-replica replication

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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

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.