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

System Properties Comparison Firebase Realtime Database vs. gStore vs. jBASE 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 native Graph DBMS to store and maintain very large RDF datasets.

A robust multi-value DBMS comprising development tools and middleware

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

Score	0.03
Rank	#367	Overall
	#37	Graph DBMS
	#18	RDF stores

Score	1.36
Rank	#157	Overall
	#3	Multivalue DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

firebase.google.com/products/realtime-database

en.gstore.cn

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.mysql.com

Technical documentation

firebase.google.com/docs/database

en.gstore.cn/#/enDocs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

dev.mysql.com/doc

Developer

Google

acquired by Google 2014

Rocket Software (formerly Zumasys)

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2016

1991

1995

Current release

1.2, November 2023

5.7

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

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

C and C++

Server operating systems

hosted

Linux

AIX
Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

schema-free and OWL/RDFS-schema support

schema-free

yes

Typing

predefined data types such as float or date

yes

optional

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

Embedded SQL for jBASE in BASIC

yes

with proprietary extensions

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API
SPARQL 1.1

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java
JavaScript
Objective-C

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

.Net
Basic
Jabbascript
Java

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

yes

Multi-source replication
Source-replica replication

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

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

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

Access rights can be defined down to the item level

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.