DBMS > Adabas vs. AgensGraph vs. Apache Drill vs. FatDB vs. SAP HANA

System Properties Comparison Adabas vs. AgensGraph vs. Apache Drill vs. FatDB 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

OLTP - DBMS for mainframes and Linux/Unix/Windows environments

used typically together with the Natural programming platform

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

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

Primary database model

Multivalue DBMS

Graph DBMS
Relational DBMS

Document store
Relational DBMS

Document store
Key-value store

Relational DBMS

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	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	0.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.softwareag.com/en_corporate/platform/adabas-natural.html

bitnine.net/agensgraph

drill.apache.org

www.sap.com/products/hana.html

Technical documentation

bitnine.net/documentation

drill.apache.org/docs

help.sap.com/hana

Developer

Software AG

Bitnine Global Inc.

Apache Software Foundation

FatCloud

SAP

Initial release

1971

2016

2012

2010

Current release

2.1, December 2018

1.20.3, January 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache Version 2

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

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
OS X
Windows

Windows

Appliance or cloud-service

Data scheme

yes

depending on used data model

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

SQL SELECT statement is SQL:2003 compliant

Via inetgration in SQL Server

yes

APIs and other access methods

HTTP API

with add-on software Adabas SOA Gateway
SOAP-based API

with add-on software Adabas SOA Gateway

Cypher Query Language
JDBC

JDBC
ODBC
RESTful HTTP API

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

JDBC
ODBC

Supported programming languages

Natural

C
Java
JavaScript
Python

C++

Server-side scripts

Stored procedures

in Natural

yes

user defined functions

yes

via applications

SQLScript, R

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

yes, with additonal products like Adabas Cluster Services, Adabas Parallel Services, Adabas Vista

no, but can be realized using table inheritance

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Source-replica replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

only with OS-specific tools (e.g. IBM RACF, CA Top Secret)

fine grained access rights according to SQL-standard

Depending on the underlying data source

Can implement custom security layer via applications

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.