DBMS > Firebase Realtime Database vs. GridGain vs. mSQL vs. SAP HANA

System Properties Comparison Firebase Realtime Database vs. GridGain vs. mSQL vs. SAP HANA

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.

GridGain is an in-memory computing platform, built on Apache Ignite

mSQL (Mini SQL) is a simple and lightweight RDBMS

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	1.26
Rank	#163	Overall
	#74	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

firebase.google.com/products/realtime-database

www.gridgain.com

hughestech.com.au/products/msql

www.sap.com/products/hana.html

Technical documentation

firebase.google.com/docs/database

www.gridgain.com/docs/index.html

help.sap.com/hana

Developer

Google

acquired by Google 2014

GridGain Systems, Inc.

Hughes Technologies

SAP

Initial release

2012

2007

1994

2010

Current release

GridGain 8.5.1

4.4, October 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

commercial, open source

commercial

free licenses can be provided

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, C++, .Net, Python, REST, SQL

Server operating systems

hosted

Linux
OS X
Solaris
Windows
z/OS

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Appliance or cloud-service

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

ANSI-99 for query and DML statements, subset of DDL

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Delphi
Java
Perl
PHP
Tcl

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes (compute grid and cache interceptors can be used instead)

SQLScript, R

Triggers

Callbacks are triggered when data changes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes

ACID

Concurrency

Support for concurrent manipulation of data

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

Role-based access control
Security Hooks for custom implementations

yes

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.