DBMS > Adabas vs. Amazon DynamoDB vs. FatDB vs. Geode vs. Hazelcast

System Properties Comparison Adabas vs. Amazon DynamoDB vs. FatDB vs. Geode vs. Hazelcast

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

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A widely adopted in-memory data grid

Primary database model

Multivalue DBMS

Document store
Key-value store

Key-value store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Website

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

aws.amazon.com/dynamodb

geode.apache.org

hazelcast.com

Technical documentation

docs.aws.amazon.com/dynamodb

geode.apache.org/docs

hazelcast.org/imdg/docs

Developer

Software AG

Amazon

FatCloud

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Hazelcast

Initial release

1971

2012

2002

2008

Current release

1.1, February 2017

5.3.6, November 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2; commercial licenses available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

Windows

All OS with a Java VM

the JDK (8 or later) is also required

All OS with a Java VM

Data scheme

yes

schema-free

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

Via inetgration in SQL Server

SQL-like query language (OQL)

SQL-like query language

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

RESTful HTTP API

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

Java Client API
Memcached protocol
RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

Supported programming languages

Natural

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Server-side scripts

Stored procedures

in Natural

yes

via applications

user defined functions

yes

Event Listeners, Executor Services

Triggers

yes

by integration with AWS Lambda

yes

via applications

yes

Cache Event Listeners

yes

Events

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

selectable replication factor

Multi-source replication

yes

Replicated Map

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Foreign keys

Referential integrity

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

yes, on a single node

one or two-phase-commit; repeatable reads; read commited

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

User concepts

Access control

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Can implement custom security layer via applications

Access rights per client and object definable

Role-based access control

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.