DBMS > Adabas vs. Ignite vs. Microsoft Azure AI Search vs. MySQL

System Properties Comparison Adabas vs. Ignite vs. Microsoft Azure AI Search vs. MySQL

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Search-as-a-service for web and mobile app development

Widely used open source RDBMS

Primary database model

Multivalue DBMS

Key-value store
Relational DBMS

Search engine

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Vector DBMS

Document store
Spatial DBMS

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

Score	3.58
Rank	#91	Overall
	#1	Multivalue DBMS

Score	3.64
Rank	#89	Overall
	#13	Key-value stores
	#48	Relational DBMS

Score	5.71
Rank	#64	Overall
	#8	Search engines

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Website

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

ignite.apache.org

azure.microsoft.com/en-us/services/search

www.mysql.com

Technical documentation

apacheignite.readme.io/docs

learn.microsoft.com/en-us/azure/search

dev.mysql.com/doc

Developer

Software AG

Apache Software Foundation

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

1971

2015

1995

Current release

Apache Ignite 2.6

8.3.0, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

yes

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

C and C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
OS X
Solaris
Windows

hosted

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

ANSI-99 for query and DML statements, subset of DDL

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

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Natural

C#
C++
Java
PHP
Python
Ruby
Scala

C#
Java
JavaScript
Python

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

yes (compute grid and cache interceptors can be used instead)

yes

proprietary syntax

Triggers

yes (cache interceptors and events)

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

Implicit feature of the cloud service

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

yes (replicated cache)

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

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

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)

Security Hooks for custom implementations

yes

using Azure authentication

Users with fine-grained authorization concept

no user groups or 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.