DBMS > Firebase Realtime Database vs. gStore vs. MySQL vs. QuestDB

System Properties Comparison Firebase Realtime Database vs. gStore vs. MySQL vs. QuestDB

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 native Graph DBMS to store and maintain very large RDF datasets.

Widely used open source RDBMS

A high performance open source SQL database for time series data

Primary database model

Document store

Graph DBMS
RDF store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.04
Rank	#359	Overall
	#37	Graph DBMS
	#18	RDF stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	2.52
Rank	#109	Overall
	#9	Time Series DBMS

Website

firebase.google.com/products/realtime-database

en.gstore.cn

www.mysql.com

questdb.io

Technical documentation

firebase.google.com/docs/database

en.gstore.cn/#/enDocs

dev.mysql.com/doc

questdb.io/docs

Developer

Google

acquired by Google 2014

Oracle

since 2010, originally MySQL AB, then Sun

QuestDB Technology Inc

Initial release

2012

2016

1995

2014

Current release

1.2, November 2023

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.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

C++

C and C++

Java (Zero-GC), C++, Rust

Server operating systems

hosted

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Data scheme

schema-free

schema-free and OWL/RDFS-schema support

yes

schema-free via InfluxDB Line Protocol

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

SQL with time-series extensions

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API
SPARQL 1.1

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

Supported programming languages

Java
JavaScript
Objective-C

C++
Java
JavaScript (Node.js)
PHP
Python

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

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by timestamps)

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication with eventual consistency

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 for single-table writes

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

through memory mapped files

User concepts

Access control

yes, based on authentication and database rules

Users, roles and permissions, Role-Based Access Control (RBAC) supported

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

QuestDB and Raspberry Pi 5 benchmark, a pocket-sized powerhouse
8 May 2024

Build your own resource monitor with QuestDB and Grafana
6 May 2024

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

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.