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

System Properties Comparison FatDB vs. OpenEdge vs. Realm vs. SAP HANA vs. Solr

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.

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

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Document store
Key-value store

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

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

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

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

www.progress.com/openedge

realm.io

www.sap.com/products/hana.html

solr.apache.org

Technical documentation

documentation.progress.com/output/ua/OpenEdge_latest

realm.io/docs

help.sap.com/hana

solr.apache.org/resources.html

Developer

FatCloud

Progress Software Corporation

Realm, acquired by MongoDB in May 2019

SAP

Apache Software Foundation

Initial release

2012

1984

2014

2010

2006

Current release

OpenEdge 12.2, March 2020

2.0 SPS07 (April 4, 2023), April 2023

9.6.0, April 2024

License

Commercial or Open Source

commercial

Open Source

commercial

Open Source

Apache Version 2

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

Java

Server operating systems

Windows

AIX
HP-UX
Linux
Solaris
Windows

Android
Backend: server-less
iOS
Windows

Appliance or cloud-service

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

Via inetgration in SQL Server

yes

close to SQL 92

yes

Solr Parallel SQL Interface

APIs and other access methods

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

JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

Progress proprietary ABL (Advanced Business Language)

.Net
Java

with Android only
Objective-C
React Native
Swift

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

via applications

yes

runs within the applications so server-side scripts are unnecessary

SQLScript, R

Java plugins

Triggers

yes

via applications

yes

Change Listeners

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

none

yes

Sharding

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

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

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

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.