DBMS > Apache Phoenix vs. Firebase Realtime Database vs. MySQL vs. YottaDB

System Properties Comparison Apache Phoenix vs. Firebase Realtime Database vs. MySQL vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

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

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

phoenix.apache.org

firebase.google.com/products/realtime-database

www.mysql.com

yottadb.com

Technical documentation

phoenix.apache.org

firebase.google.com/docs/database

dev.mysql.com/doc

yottadb.com/resources/documentation

Developer

Apache Software Foundation

Google

acquired by Google 2014

Oracle

since 2010, originally MySQL AB, then Sun

YottaDB, LLC

Initial release

2014

2012

1995

2001

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL 3.0

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 and C++

Server operating systems

Linux
Unix
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

schema-free

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

by using the Octo plugin

APIs and other access methods

JDBC

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

user defined functions

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
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

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

ACID

yes

ACID

not for MyISAM storage engine

optimistic locking

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

yes, based on authentication and database rules

Users with fine-grained authorization concept

no user groups or roles

Users and groups based on OS-security mechanisms

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.