DBMS > Firebase Realtime Database vs. Google Cloud Spanner vs. Immudb vs. MySQL

System Properties Comparison Firebase Realtime Database vs. Google Cloud Spanner vs. Immudb 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.

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Relational DBMS

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	2.69
Rank	#101	Overall
	#51	Relational DBMS

Score	0.24
Rank	#295	Overall
	#42	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

firebase.google.com/products/realtime-database

cloud.google.com/spanner

github.com/codenotary/immudb
immudb.io

www.mysql.com

Technical documentation

firebase.google.com/docs/database

cloud.google.com/spanner/docs

docs.immudb.io

dev.mysql.com/doc

Developer

Google

acquired by Google 2014

Google

Codenotary

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2017

2020

1995

Current release

1.2.3, April 2022

9.0.0, July 2024

License

Commercial or Open Source

commercial

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

yes

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

hosted

BSD
Linux
macOS
Solaris
Windows
z/OS

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

Secondary indexes

yes

SQL

Support of SQL

yes

Query statements complying to ANSI 2011

SQL-like syntax

yes

with proprietary extensions

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

gRPC protocol
PostgreSQL wire protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java
JavaScript
Objective-C

Go
Java
JavaScript (Node.js)
Python

.Net
Go
Java
JavaScript (Node.js)
Python

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

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication with 3 replicas for regional instances.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID

Strict serializable isolation

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

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 rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.