DBMS > Dolt vs. FatDB vs. OpenEdge vs. Realm vs. SAP HANA

System Properties Comparison Dolt vs. FatDB 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 MySQL compatible DBMS with Git-like versioning of data and schema

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

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

Relational DBMS

Document store
Key-value store

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

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

github.com/dolthub/dolt
www.dolthub.com

www.progress.com/openedge

realm.io

www.sap.com/products/hana.html

Technical documentation

docs.dolthub.com

documentation.progress.com/output/ua/OpenEdge_latest

realm.io/docs

help.sap.com/hana

Developer

DoltHub Inc

FatCloud

Progress Software Corporation

Realm, acquired by MongoDB in May 2019

SAP

Initial release

2018

2012

1984

2014

2010

Current release

OpenEdge 12.2, March 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

commercial

Cloud-based only

Only available as a cloud service

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

Linux
macOS
Windows

Windows

AIX
HP-UX
Linux
Solaris
Windows

Android
Backend: server-less
iOS
Windows

Appliance or cloud-service

Data scheme

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

Secondary indexes

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

close to SQL 92

yes

APIs and other access methods

CLI Client
HTTP REST

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

JDBC
ODBC

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Progress proprietary ABL (Advanced Business Language)

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

via applications

yes

runs within the applications so server-side scripts are unnecessary

SQLScript, R

Triggers

yes

via applications

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

since Version 11.4

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

Only one user is configurable, and must be specified in the config file at startup

Can implement custom security layer via applications

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.