DBMS > Adabas vs. EsgynDB vs. Infobright vs. MySQL vs. ToroDB

System Properties Comparison Adabas vs. EsgynDB vs. Infobright vs. MySQL vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

OLTP - DBMS for mainframes and Linux/Unix/Windows environments

used typically together with the Natural programming platform

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Widely used open source RDBMS

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Multivalue DBMS

Relational DBMS

Key/Value like access via memcached API

Document store

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.25
Rank	#312	Overall
	#138	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

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

www.esgyn.cn

ignitetech.com/softwarelibrary/infobrightdb

www.mysql.com

github.com/torodb/server

Technical documentation

dev.mysql.com/doc

Developer

Software AG

Esgyn

Ignite Technologies Inc.; formerly InfoBright Inc.

Oracle

since 2010, originally MySQL AB, then Sun

8Kdata

Initial release

1971

2015

2005

1995

2016

Current release

8.4.0, April 2024

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL-V3

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

C and C++

Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

with proprietary extensions

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Natural

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

in Natural

Java Stored Procedures

yes

proprietary syntax

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

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-source replication between multi datacenters

Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication

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
Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

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

User concepts

Access control

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

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.