DBMS > Badger vs. Ehcache vs. Firebase Realtime Database vs. MySQL

System Properties Comparison Badger vs. Ehcache vs. Firebase Realtime Database 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.

A widely adopted Java cache with tiered storage options

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Widely used open source RDBMS

Primary database model

Key-value store

Document store

Relational DBMS

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	#328	Overall
	#48	Key-value stores

Score	4.79
Rank	#66	Overall
	#8	Key-value stores

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

github.com/dgraph-io/badger

www.ehcache.org

firebase.google.com/products/realtime-database

www.mysql.com

Technical documentation

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

www.ehcache.org/documentation

firebase.google.com/docs/database

dev.mysql.com/doc

Developer

DGraph Labs

Terracotta Inc, owned by Software AG

Google

acquired by Google 2014

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2017

2009

2012

1995

Current release

3.10.0, March 2022

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

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

Java

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

hosted

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

JCache

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java

Java
JavaScript
Objective-C

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

limited functionality with using 'rules'

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

by using Terracotta Server

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

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

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

yes

supports JTA and can work as an XA resource

yes

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

yes, based on authentication and database rules

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.