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

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

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

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	14.29
Rank	#39	Overall
	#6	Document stores

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

firebase.google.com/products/realtime-database

hbase.apache.org

github.com/google/leveldb

www.mysql.com

Technical documentation

firebase.google.com/docs/database

hbase.apache.org/book.html

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

dev.mysql.com/doc

Developer

Google

acquired by Google 2014

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Google

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2008

2011

1995

Current release

2.3.4, January 2021

1.23, February 2021

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C++

C and C++

Server operating systems

hosted

Linux
Unix
Windows

using Cygwin

Illumos
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

schema-free, schema definition possible

schema-free

yes

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

Android
iOS
JavaScript API
RESTful HTTP API

Java API
RESTful HTTP API
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java
JavaScript
Objective-C

C
C#
C++
Groovy
Java
PHP
Python
Scala

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'

yes

Coprocessors in Java

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

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency or Eventual Consistency

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

Single row ACID (across millions of columns)

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

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

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.