DBMS > Amazon DocumentDB vs. JanusGraph vs. OpenEdge vs. Realm vs. SAP HANA

System Properties Comparison Amazon DocumentDB vs. JanusGraph vs. OpenEdge vs. Realm vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

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	1.91
Rank	#132	Overall
	#24	Document stores

Score	1.94
Rank	#129	Overall
	#12	Graph 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

aws.amazon.com/documentdb

janusgraph.org

www.progress.com/openedge

realm.io

www.sap.com/products/hana.html

Technical documentation

aws.amazon.com/documentdb/resources

docs.janusgraph.org

documentation.progress.com/output/ua/OpenEdge_latest

realm.io/docs

help.sap.com/hana

Developer

Linux Foundation; originally developed as Titan by Aurelius

Progress Software Corporation

Realm, acquired by MongoDB in May 2019

SAP

Initial release

2019

2017

1984

2014

2010

Current release

0.6.3, February 2023

OpenEdge 12.2, March 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

Java

Server operating systems

hosted

Linux
OS X
Unix
Windows

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

yes

close to SQL 92

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

Clojure
Java
Python

Progress proprietary ABL (Advanced Business Language)

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

yes

runs within the applications so server-side scripts are unnecessary

SQLScript, R

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

horizontal partitioning

since Version 11.4

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Relationships in graphs

yes

Transaction concepts

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

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

Access rights for users and roles

User authentification and security via Rexster Graph Server

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.