DBMS > Firebase Realtime Database vs. HyperSQL vs. MySQL vs. SQream DB

System Properties Comparison Firebase Realtime Database vs. HyperSQL vs. MySQL vs. SQream DB

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.

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Widely used open source RDBMS

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

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	3.14
Rank	#85	Overall
	#46	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.62
Rank	#234	Overall
	#109	Relational DBMS

Website

firebase.google.com/products/realtime-database

hsqldb.org

www.mysql.com

sqream.com

Technical documentation

firebase.google.com/docs/database

hsqldb.org/web/hsqlDocsFrame.html

dev.mysql.com/doc

docs.sqream.com

Developer

Google

acquired by Google 2014

Oracle

since 2010, originally MySQL AB, then Sun

SQream Technologies

Initial release

2012

2001

1995

2017

Current release

2.7.2, June 2023

9.0.0, July 2024

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

based on BSD license

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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

C++, CUDA, Haskell, Java, Scala

Server operating systems

hosted

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API

JDBC via HTTP
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

.Net
JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

All languages supporting JDBC/ODBC
Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Java, SQL

yes

proprietary syntax

user defined functions in Python

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

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

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

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

fine grained access rights according to SQL-standard

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.