DBMS > etcd vs. IBM Db2 Event Store vs. MySQL vs. SQLite

System Properties Comparison etcd vs. IBM Db2 Event Store vs. MySQL vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

Distributed Event Store optimized for Internet of Things use cases

Widely used open source RDBMS

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Event Store
Time Series DBMS

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	7.05
Rank	#53	Overall
	#5	Key-value stores

Score	0.18
Rank	#315	Overall
	#2	Event Stores
	#26	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

etcd.io
github.com/etcd-io/etcd

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

www.mysql.com

www.sqlite.org

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

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

dev.mysql.com/doc

www.sqlite.org/docs.html

Developer

IBM

Oracle

since 2010, originally MySQL AB, then Sun

Dwayne Richard Hipp

Initial release

2017

1995

2000

Current release

3.4, August 2019

2.0

9.0.0, July 2024

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free developer edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Public Domain

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.

Implementation language

C and C++

Server operating systems

FreeBSD
Linux
Windows

experimental

Linux

Linux, macOS, Windows for the developer addition

FreeBSD
Linux
OS X
Solaris
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

through the embedded Spark runtime

yes

with proprietary extensions

yes

SQL-92 is not fully supported

APIs and other access methods

gRPC
JSON over HTTP

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Active-active shard replication

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

table locks or row locks depending on storage engine

yes

via file-system locks

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.