DBMS > Firebase Realtime Database vs. Greenplum vs. Hazelcast vs. SAP HANA

System Properties Comparison Firebase Realtime Database vs. Greenplum vs. Hazelcast 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.

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

A widely adopted in-memory data grid

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

Primary database model

Secondary database models

Document store
Spatial DBMS

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

firebase.google.com/products/realtime-database

greenplum.org

hazelcast.com

www.sap.com/products/hana.html

Technical documentation

firebase.google.com/docs/database

docs.greenplum.org

hazelcast.org/imdg/docs

help.sap.com/hana

Developer

Google

acquired by Google 2014

Pivotal Software Inc.

Hazelcast

SAP

Initial release

2012

2005

2008

2010

Current release

7.0.0, September 2023

5.3.6, November 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

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

Linux

All OS with a Java VM

Appliance or cloud-service

Data scheme

schema-free

yes

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

since Version 4.2

yes

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

C
Java
Perl
Python
R

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

Event Listeners, Executor Services

SQLScript, R

Triggers

Callbacks are triggered when data changes

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Replicated Map

yes

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

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

one or two-phase-commit; repeatable reads; read commited

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

fine grained access rights according to SQL-standard

Role-based access control

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.