DBMS > Adabas vs. Machbase Neo vs. PostGIS vs. Riak KV

System Properties Comparison Adabas vs. Machbase Neo vs. PostGIS vs. Riak KV

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

TimeSeries DBMS for AIoT and BigData

Spatial extension of PostgreSQL

Distributed, fault tolerant key-value store

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Relational DBMS

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

Score	3.58
Rank	#91	Overall
	#1	Multivalue DBMS

Score	0.22
Rank	#324	Overall
	#29	Time Series DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

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

machbase.com

postgis.net

Technical documentation

machbase.com/dbms

postgis.net/documentation

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Software AG

Machbase

OpenSource, formerly Basho Technologies

Initial release

1971

2013

2005

2009

Current release

V8.0, August 2023

3.4.2, February 2024

3.2.0, December 2022

License

Commercial or Open Source

commercial

free test version available

Open Source

GPL v2.0

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
macOS
Windows

Linux
OS X

Data scheme

yes

schema-free

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

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

SQL-like query language

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

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

Natural

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

in Natural

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

yes

based on PostgreSQL

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

selectable replication factor

yes

based on PostgreSQL

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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

In-memory capabilities

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

yes

volatile and lookup table

User concepts

Access control

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

simple password-based access control

yes

based on PostgreSQL

yes, using Riak Security

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

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

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

COBOL Is Taking Heat, but These Other Legacy Languages Could Burn You
1 October 2020, DevOps.com

Don't rewrite legacy systems for hybrid cloud – integrate them
1 February 2022, ITWeb

The top five green screen systems that run Australia
25 September 2015, iTnews

provided by Google News

“Luxembourg is a perfect target area”: Korean accelerator exec
27 October 2022, Delano.lu

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page