DBMS > 4D vs. Adabas vs. Amazon Redshift vs. Databend vs. Ignite

System Properties Comparison 4D vs. Adabas vs. Amazon Redshift vs. Databend vs. Ignite

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

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

Relational DBMS

Multivalue DBMS

Relational DBMS

Key-value store
Relational DBMS

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.34
Rank	#283	Overall
	#130	Relational DBMS

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

Website

www.4d.com

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

aws.amazon.com/redshift

github.com/datafuselabs/databend
www.databend.com

ignite.apache.org

Technical documentation

developer.4d.com

docs.aws.amazon.com/redshift

docs.databend.com

apacheignite.readme.io/docs

Developer

4D, Inc

Software AG

Amazon (based on PostgreSQL)

Databend Labs

Apache Software Foundation

Initial release

1984

1971

2012

2021

2015

Current release

v20, April 2023

1.0.59, April 2023

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

Apache Version 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

Rust

C++, Java, .Net

Server operating systems

OS X
Windows

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

hosted
Linux
macOS

Linux
OS X
Solaris
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.

yes

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

close to SQL 92

yes

with add-on product Adabas SQL Gateway

yes

does not fully support an SQL-standard

yes

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

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

HTTP API

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

with add-on software Adabas SOA Gateway

JDBC
ODBC

CLI Client
JDBC
RESTful HTTP API

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

Supported programming languages

4D proprietary IDE
PHP

Natural

All languages supporting JDBC/ODBC

Go
Java
JavaScript (Node.js)
Python
Rust

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

in Natural

user defined functions

in Python

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

Triggers

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

none

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

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, with add-on product Event Replicator

yes

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

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

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

Users and groups

only with OS-specific tools (e.g. IBM RACF, CA Top Secret)

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles

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.