DBMS > Firebase Realtime Database vs. KeyDB vs. LevelDB vs. MySQL

System Properties Comparison Firebase Realtime Database vs. KeyDB vs. LevelDB vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Widely used open source RDBMS

Primary database model

Document store

Key-value 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	13.60
Rank	#39	Overall
	#6	Document stores

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Score	2.33
Rank	#111	Overall
	#19	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

firebase.google.com/products/realtime-database

github.com/Snapchat/KeyDB
keydb.dev

github.com/google/leveldb

www.mysql.com

Technical documentation

firebase.google.com/docs/database

docs.keydb.dev

github.com/google/leveldb/blob/main/doc/index.md

dev.mysql.com/doc

Developer

Google

acquired by Google 2014

EQ Alpha Technology Ltd.

Google

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2019

2011

1995

Current release

1.23, February 2021

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

BSD-3

Open Source

BSD

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

C++

C and C++

Server operating systems

hosted

Linux

Illumos
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java
JavaScript
Objective-C

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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'

Lua

yes

proprietary syntax

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

none

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

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency
Strong eventual consistency with CRDTs

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

Optimistic locking, atomic execution of commands blocks and scripts

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

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

with automatic compression on writes

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

simple password-based access control and ACL

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.