DBMS > Adabas vs. Amazon Redshift vs. Google Cloud Spanner vs. HEAVY.AI vs. mSQL

System Properties Comparison Adabas vs. Amazon Redshift vs. Google Cloud Spanner vs. HEAVY.AI vs. mSQL

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

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Primary database model

Multivalue DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	2.89
Rank	#103	Overall
	#52	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Website

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

aws.amazon.com/redshift

cloud.google.com/spanner

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

hughestech.com.au/products/msql

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/spanner/docs

docs.heavy.ai

Developer

Software AG

Amazon (based on PostgreSQL)

Google

HEAVY.AI, Inc.

Hughes Technologies

Initial release

1971

2012

2017

2016

1994

Current release

5.10, January 2022

4.4, October 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

free licenses can be provided

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

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

Linux

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

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

restricted

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

does not fully support an SQL-standard

yes

Query statements complying to ANSI 2011

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

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
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

JDBC
ODBC

Supported programming languages

Natural

All languages supporting JDBC/ODBC

Go
Java
JavaScript (Node.js)
Python

All languages supporting JDBC/ODBC/Thrift
Python

C
C++
Delphi
Java
Perl
PHP
Tcl

Server-side scripts

Stored procedures

in Natural

user defined functions

in Python

Triggers

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

Multi-source replication with 3 replicas for regional instances.

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

ACID

Strict serializable isolation

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

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.