DBMS > Adabas vs. Amazon DynamoDB vs. FatDB vs. Google Cloud Datastore

System Properties Comparison Adabas vs. Amazon DynamoDB vs. FatDB vs. Google Cloud Datastore

Please select another system to include it in the comparison.

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.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Primary database model

Multivalue DBMS

Document store
Key-value store

Document store

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

Score	2.64
Rank	#104	Overall
	#1	Multivalue DBMS

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

Website

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

aws.amazon.com/dynamodb

cloud.google.com/datastore

Technical documentation

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

Developer

Software AG

Amazon

FatCloud

Google

Initial release

1971

2012

2008

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

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

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

Windows

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

Via inetgration in SQL Server

SQL-like query language (GQL)

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

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Supported programming languages

Natural

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

in Natural

yes

via applications

using Google App Engine

Triggers

yes

by integration with AWS Lambda

yes

via applications

Callbacks using the Google Apps Engine

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 using Paxos

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

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

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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.

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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.