DBMS > Adabas vs. Machbase Neo vs. MySQL vs. Valentina Server vs. WakandaDB

System Properties Comparison Adabas vs. Machbase Neo vs. MySQL vs. Valentina Server vs. WakandaDB

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

Widely used open source RDBMS

Object-relational database and reports server

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Multivalue DBMS

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

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

Technical documentation

machbase.com/dbms

dev.mysql.com/doc

valentina-db.com/docs/dokuwiki/v5/doku.php

wakanda.github.io/doc

Developer

Software AG

Machbase

Oracle

since 2010, originally MySQL AB, then Sun

Paradigma Software

Wakanda SAS

Initial release

1971

2013

1995

1999

2012

Current release

V8.0, August 2023

8.4.0, April 2024

5.7.5

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

free test version available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

AGPLv3, 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

C++, JavaScript

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

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

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

SQL-like query language

yes

with proprietary extensions

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

ADO.NET
JDBC
ODBC
Proprietary native API

ODBC

RESTful HTTP API

Supported programming languages

Natural

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

JavaScript

Server-side scripts

Stored procedures

in Natural

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

selectable replication factor

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

yes

User concepts

Access control

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

simple password-based access control

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

yes

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.