DBMS > Adabas vs. BigObject vs. Memcached vs. MySQL vs. Valentina Server

System Properties Comparison Adabas vs. BigObject vs. Memcached vs. MySQL vs. Valentina Server

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

Analytic DBMS for real-time computations and queries

In-memory key-value store, originally intended for caching

Widely used open source RDBMS

Object-relational database and reports server

Primary database model

Multivalue DBMS

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

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

Technical documentation

docs.bigobject.io

github.com/memcached/memcached/wiki

dev.mysql.com/doc

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

Developer

Software AG

BigObject, Inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

since 2010, originally MySQL AB, then Sun

Paradigma Software

Initial release

1971

2015

2003

1995

1999

Current release

1.6.25, March 2024

8.4.0, April 2024

5.7.5

License

Commercial or Open Source

commercial

free community edition available

Open Source

BSD license

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

FreeBSD
Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

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 DML and DDL statements

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

fluentd
ODBC
RESTful HTTP API

Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

ODBC

Supported programming languages

Natural

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

in Natural

Lua

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

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

table locks or row locks depending on storage engine

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

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

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.