DBMS > Firebase Realtime Database vs. MySQL vs. SAP SQL Anywhere vs. TigerGraph

System Properties Comparison Firebase Realtime Database vs. MySQL vs. SAP SQL Anywhere vs. TigerGraph

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.

Widely used open source RDBMS

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	15.00
Rank	#39	Overall
	#6	Document stores

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Score	1.83
Rank	#141	Overall
	#13	Graph DBMS

Website

firebase.google.com/products/realtime-database

www.mysql.com

www.sap.com/products/technology-platform/sql-anywhere.html

www.tigergraph.com

Technical documentation

firebase.google.com/docs/database

dev.mysql.com/doc

help.sap.com/docs/SAP_SQL_Anywhere

docs.tigergraph.com

Developer

Google

acquired by Google 2014

Oracle

since 2010, originally MySQL AB, then Sun

SAP

formerly Sybase

Initial release

2012

1995

1992

2017

Current release

8.3.0, January 2024

17, July 2015

License

Commercial or Open Source

commercial

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux

Data scheme

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

with proprietary extensions

yes

SQL-like query language (GSQL)

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
HTTP API
JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

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
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

proprietary syntax

yes, in C/C++, Java, .Net or Perl

yes

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

yes

Relationships in graphs

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

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Role-based access control

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.