DBMS > Badger vs. EDB Postgres vs. etcd vs. MySQL

System Properties Comparison Badger vs. EDB Postgres vs. etcd vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

A distributed reliable key-value store

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	1.90
Rank	#135	Overall
	#63	Relational DBMS

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

github.com/dgraph-io/badger

www.enterprisedb.com

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

www.mysql.com

Technical documentation

godoc.org/github.com/dgraph-io/badger

www.enterprisedb.com/docs

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

dev.mysql.com/doc

Developer

DGraph Labs

EnterpriseDB

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2017

2005

1995

Current release

14, December 2021

3.4, August 2019

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

BSD for PostgreSQL-components

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

BSD
Linux
OS X
Solaris
Windows

Linux
Windows

FreeBSD
Linux
Windows

experimental

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard with numerous extensions

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

gRPC
JSON over HTTP

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

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

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

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

proprietary syntax

Triggers

yes

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

by hash, list or range

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

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.