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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

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

Primary database model

Document store
Key-value store

Document store

Key-value store
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.64
Rank	#39	Overall
	#6	Document stores

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

firebase.google.com/products/realtime-database

www.gridgain.com

www.sap.com/products/hana.html

Technical documentation

firebase.google.com/docs/database

www.gridgain.com/docs/index.html

help.sap.com/hana

Developer

FatCloud

Google

acquired by Google 2014

GridGain Systems, Inc.

SAP

Initial release

2012

2007

2010

Current release

GridGain 8.5.1

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

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

Server operating systems

Windows

hosted

Linux
OS X
Solaris
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

Via inetgration in SQL Server

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

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

Server-side scripts

Stored procedures

yes

via applications

limited functionality with using 'rules'

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

SQLScript, R

Triggers

yes

via applications

Callbacks are triggered when data changes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

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

Can implement custom security layer via applications

yes, based on authentication and database rules

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.