DBMS > Adabas vs. Amazon Neptune vs. Amazon Redshift vs. Elasticsearch

System Properties Comparison Adabas vs. Amazon Neptune vs. Amazon Redshift vs. Elasticsearch

Please select another system to include it in the comparison.

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

Fast, reliable graph database built for the cloud

Large scale data warehouse service for use with business intelligence tools

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	2.29
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	132.83
Rank	#7	Overall
	#1	Search engines

Website

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

aws.amazon.com/neptune

aws.amazon.com/redshift

www.elastic.co/elasticsearch

Technical documentation

aws.amazon.com/neptune/developer-resources

docs.aws.amazon.com/redshift

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

Developer

Software AG

Amazon

Amazon (based on PostgreSQL)

Elastic

Initial release

1971

2017

2012

2010

Current release

8.6, January 2023

License

Commercial or Open Source

commercial

Open Source

Elastic License

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

Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

All OS with a Java VM

Data scheme

yes

schema-free

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

does not fully support an SQL-standard

SQL-like query language

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

Natural

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

in Natural

user defined functions

in Python

yes

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Memcached and Redis integration

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)

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.