DBMS > Adabas vs. Amazon Redshift vs. Ehcache vs. Graphite vs. Ignite

System Properties Comparison Adabas vs. Amazon Redshift vs. Ehcache vs. Graphite vs. Ignite

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 widely adopted Java cache with tiered storage options

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Primary database model

Key-value store
Relational 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.64
Rank	#68	Overall
	#8	Key-value stores

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Website

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

aws.amazon.com/redshift

www.ehcache.org

github.com/graphite-project/graphite-web

ignite.apache.org

Technical documentation

docs.aws.amazon.com/redshift

www.ehcache.org/documentation

graphite.readthedocs.io

apacheignite.readme.io/docs

Developer

Software AG

Amazon (based on PostgreSQL)

Terracotta Inc, owned by Software AG

Chris Davis

Apache Software Foundation

Initial release

1971

2012

2009

2006

2015

Current release

3.10.0, March 2022

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

Apache 2.0

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

Python

C++, Java, .Net

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

All OS with a Java VM

Linux
Unix

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

does not fully support an SQL-standard

ANSI-99 for query and DML statements, subset of DDL

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

JCache

HTTP API
Sockets

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

Natural

All languages supporting JDBC/ODBC

Java

JavaScript (Node.js)
Python

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

in Natural

user defined functions

in Python

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

by using Terracotta Server

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

by using Terracotta Server

none

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

Security Hooks for custom implementations

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.