DBMS > Adabas vs. EJDB vs. Microsoft Azure Data Explorer vs. MySQL vs. Realm

System Properties Comparison Adabas vs. EJDB vs. Microsoft Azure Data Explorer vs. MySQL vs. Realm

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Fully managed big data interactive analytics platform

Widely used open source RDBMS

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

column oriented

Key/Value like access via memcached API

Document store

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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.27
Rank	#297	Overall
	#44	Document stores

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Website

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

github.com/Softmotions/ejdb

azure.microsoft.com/services/data-explorer

www.mysql.com

realm.io

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

docs.microsoft.com/en-us/azure/data-explorer

dev.mysql.com/doc

realm.io/docs

Developer

Software AG

Softmotions

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Realm, acquired by MongoDB in May 2019

Initial release

1971

2012

2019

1995

2014

Current release

cloud service with continuous releases

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

GPLv2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

server-less

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Android
Backend: server-less
iOS
Windows

Data scheme

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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

all fields are automatically indexed

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

Kusto Query Language (KQL), SQL subset

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

in-process shared library

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Natural

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

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

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

in Natural

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

runs within the applications so server-side scripts are unnecessary

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

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

none

Sharding

Implicit feature of the cloud service

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

none

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

In-Memory realm

User concepts

Access control

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

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

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.