DBMS > Adabas vs. Apache Druid vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. STSdb

System Properties Comparison Adabas vs. Apache Druid vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. STSdb

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

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Globally distributed, horizontally scalable, multi-model database service

Fully managed big data interactive analytics platform

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Multivalue DBMS

Relational DBMS
Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

column oriented

Key-value store

Secondary database models

Spatial DBMS

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

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

Score	3.58
Rank	#91	Overall
	#1	Multivalue DBMS

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	29.85
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	5.16
Rank	#69	Overall
	#37	Relational DBMS

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

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

druid.apache.org

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/services/data-explorer

github.com/STSSoft/STSdb4

Technical documentation

druid.apache.org/docs/latest/design

learn.microsoft.com/azure/cosmos-db

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

Developer

Software AG

Apache Software Foundation and contributors

Microsoft

STS Soft SC

Initial release

1971

2012

2014

2019

2011

Current release

29.0.1, April 2024

cloud service with continuous releases

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

Open Source

GPLv2, commercial license 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.

Implementation language

Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
OS X
Unix

hosted

Windows

Data scheme

yes

schema-less columns are supported

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

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

yes

primitive types and user defined types (classes)

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 properties auto-indexed by default

all fields are automatically indexed

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

SQL for querying

SQL-like query language

Kusto Query Language (KQL), SQL subset

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

JDBC
RESTful HTTP/JSON API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

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

.NET Client API

Supported programming languages

Natural

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

C#
Java

Server-side scripts

Stored procedures

in Natural

JavaScript

Yes, possible languages: KQL, Python, R

Triggers

JavaScript

yes

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

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

manual/auto, time-based

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes, via HDFS, S3 or other storage engines

yes

Implicit feature of the cloud service

yes

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights can be defined down to the item level

Azure Active Directory Authentication

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.