DBMS > Firebase Realtime Database vs. Geode vs. Microsoft Azure Table Storage vs. SAP HANA

System Properties Comparison Firebase Realtime Database vs. Geode vs. Microsoft Azure Table Storage 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.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A Wide Column Store for rapid development using massive semi-structured datasets

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

Primary database model

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.86
Rank	#134	Overall
	#24	Key-value stores

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

firebase.google.com/products/realtime-database

geode.apache.org

azure.microsoft.com/en-us/services/storage/tables

www.sap.com/products/hana.html

Technical documentation

firebase.google.com/docs/database

geode.apache.org/docs

help.sap.com/hana

Developer

Google

acquired by Google 2014

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Microsoft

SAP

Initial release

2012

2002

2012

2010

Current release

1.1, February 2017

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

hosted

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP API

JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

SQLScript, R

Triggers

Callbacks are triggered when data changes

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

yes, on a single node

optimistic locking

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

Access rights per client and object definable

Access rights based on private key authentication or shared access signatures

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.