DBMS > FatDB vs. Firebase Realtime Database vs. OpenEdge vs. Realm vs. SAP HANA

System Properties Comparison FatDB vs. Firebase Realtime Database vs. OpenEdge vs. Realm vs. SAP HANA

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.

Application development environment with integrated database management system

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

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

Primary database model

Document store
Key-value store

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	14.29
Rank	#39	Overall
	#6	Document stores

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

firebase.google.com/products/realtime-database

www.progress.com/openedge

realm.io

www.sap.com/products/hana.html

Technical documentation

firebase.google.com/docs/database

documentation.progress.com/output/ua/OpenEdge_latest

realm.io/docs

help.sap.com/hana

Developer

FatCloud

Google

acquired by Google 2014

Progress Software Corporation

Realm, acquired by MongoDB in May 2019

SAP

Initial release

2012

1984

2014

2010

Current release

OpenEdge 12.2, March 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

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

Server operating systems

Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows

Android
Backend: server-less
iOS
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

yes

close to SQL 92

yes

APIs and other access methods

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

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

Progress proprietary ABL (Advanced Business Language)

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

yes

via applications

limited functionality with using 'rules'

yes

runs within the applications so server-side scripts are unnecessary

SQLScript, R

Triggers

yes

via applications

Callbacks are triggered when data changes

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

In-Memory realm

yes

User concepts

Access control

Can implement custom security layer via applications

yes, based on authentication and database rules

Users and groups

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.