DBMS > 4D vs. Adabas vs. Atos Standard Common Repository vs. GeoMesa vs. OpenQM

System Properties Comparison 4D vs. Adabas vs. Atos Standard Common Repository vs. GeoMesa vs. OpenQM

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

QpenQM is a high-performance, self-tuning, multi-value DBMS

Primary database model

Relational DBMS

Multivalue DBMS

Document store
Key-value store

Spatial DBMS

Multivalue DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Website

www.4d.com

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

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.geomesa.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

Technical documentation

developer.4d.com

www.geomesa.org/documentation/stable/user/index.html

Developer

4D, Inc

Software AG

Atos Convergence Creators

CCRi and others

Rocket Software, originally Martin Phillips

Initial release

1984

1971

2016

2014

1993

Current release

v20, April 2023

1703

4.0.5, February 2024

3.4-12

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

GPLv2, extended commercial license available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Scala

Server operating systems

OS X
Windows

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

yes

Schema and schema-less with LDAP views

yes

with some exceptions

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

yes

close to SQL 92

yes

with add-on product Adabas SQL Gateway

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

LDAP

Supported programming languages

4D proprietary IDE
PHP

Natural

All languages with LDAP bindings

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

yes

in Natural

yes

Triggers

yes

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

cell division

depending on storage layer

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, with add-on product Event Replicator

yes

depending on storage layer

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

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

depending on storage layer

User concepts

Access control

Users and groups

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

LDAP bind authentication

yes

depending on the DBMS used for storage

Access rights can be defined down to the item level

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Modernize Natural and Adabas Workloads on AWS with Advanced's Application Transparency Platform | Amazon Web ...
1 April 2024, AWS Blog

State agency proves DevOps and mainframes can coexist
12 April 2024, SiliconANGLE News

Deploying Software AG Adabas and Natural Workloads on AWS | Amazon Web Services
25 May 2021, AWS Blog

IBM buys 50-year-old Software AG's enterprise tech units for €2.13B in cash
18 December 2023, The Register

A Second Look at LzLabs' Mainframe Migration
28 June 2017, Virtualization Review

provided by Google News

Share this page