DBMS > Adabas vs. Google Cloud Datastore vs. SAP HANA vs. Teradata Aster

System Properties Comparison Adabas vs. Google Cloud Datastore vs. SAP HANA vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

used typically together with the Natural programming platform

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

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

Platform for big data analytics on multistructured data sources and types

Primary database model

Multivalue DBMS

Document 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	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

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

cloud.google.com/datastore

www.sap.com/products/hana.html

Technical documentation

cloud.google.com/datastore/docs

help.sap.com/hana

Developer

Software AG

Google

SAP

Teradata

Initial release

1971

2008

2010

2005

Current release

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or 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.

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

Appliance or cloud-service

Linux

Data scheme

yes

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

yes

yes, details here

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

SQL-like query language (GQL)

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

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

JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

Natural

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

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

in Natural

using Google App Engine

SQLScript, R

R packages

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-source replication using Paxos

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

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.

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

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

yes

fine grained access rights according to SQL-standard

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.