DBMS > Adabas vs. Amazon Redshift vs. Google Cloud Datastore vs. HEAVY.AI vs. TigerGraph

System Properties Comparison Adabas vs. Amazon Redshift vs. Google Cloud Datastore vs. HEAVY.AI vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

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

used typically together with the Natural programming platform

Large scale data warehouse service for use with business intelligence tools

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Secondary database models

Spatial DBMS

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

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

aws.amazon.com/redshift

cloud.google.com/datastore

github.com/heavyai/heavydb
www.heavy.ai

www.tigergraph.com

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/datastore/docs

docs.heavy.ai

docs.tigergraph.com

Developer

Software AG

Amazon (based on PostgreSQL)

Google

HEAVY.AI, Inc.

Initial release

1971

2012

2008

2016

2017

Current release

5.10, January 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

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

C++ and CUDA

C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

Linux

Data scheme

yes

schema-free

yes

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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

does not fully support an SQL-standard

SQL-like query language (GQL)

yes

SQL-like query language (GSQL)

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

JDBC
ODBC

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

JDBC
ODBC
Thrift
Vega

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

Natural

All languages supporting JDBC/ODBC

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

All languages supporting JDBC/ODBC/Thrift
Python

C++
Java

Server-side scripts

Stored procedures

in Natural

user defined functions

in Python

using Google App Engine

yes

Triggers

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

Round robin

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

Multi-source replication using Paxos

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

yes

Relationships in graphs

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)

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

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.