DBMS > Adabas vs. Amazon Redshift vs. Graph Engine vs. KeyDB vs. Microsoft Azure SQL Database

System Properties Comparison Adabas vs. Amazon Redshift vs. Graph Engine vs. KeyDB vs. Microsoft Azure SQL Database

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 distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Database as a Service offering with high compatibility to Microsoft SQL Server

Primary database model

Multivalue DBMS

Relational DBMS

Graph DBMS
Key-value store

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS
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	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Website

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

aws.amazon.com/redshift

www.graphengine.io

github.com/Snapchat/KeyDB
keydb.dev

azure.microsoft.com/en-us/products/azure-sql/database

Technical documentation

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

docs.keydb.dev

docs.microsoft.com/en-us/azure/azure-sql

Developer

Software AG

Amazon (based on PostgreSQL)

Microsoft

EQ Alpha Technology Ltd.

Microsoft

Initial release

1971

2012

2010

2019

2010

Current release

V12

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

BSD-3

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

.NET and C

C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

.NET

Linux

hosted

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

Secondary indexes

yes

restricted

yes

by using the Redis Search module

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

does not fully support an SQL-standard

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

JDBC
ODBC

RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
ODBC

Supported programming languages

Natural

All languages supporting JDBC/ODBC

C#
C++
F#
Visual Basic

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

in Natural

user defined functions

in Python

yes

Lua

Transact SQL

Triggers

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

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

Multi-source replication
Source-replica replication

yes, with always 3 replicas available

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control and ACL

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.