DBMS > Microsoft Azure Data Explorer vs. MySQL vs. OrigoDB vs. Qdrant vs. SAP Advantage Database Server

System Properties Comparison Microsoft Azure Data Explorer vs. MySQL vs. OrigoDB vs. Qdrant vs. SAP Advantage Database Server

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Fully managed big data interactive analytics platform

Widely used open source RDBMS

A fully ACID in-memory object graph database

A high-performance vector database with neural network or semantic-based matching

Low-cost RDBMS with access to ISAM and FoxPro data structures

Primary database model

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Document store
Object oriented DBMS

Vector DBMS

Relational DBMS

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	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

azure.microsoft.com/services/data-explorer

www.mysql.com

origodb.com

github.com/qdrant/qdrant
qdrant.tech

www.sap.com/products/advantage-database-server.html

Technical documentation

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

dev.mysql.com/doc

origodb.com/docs

qdrant.tech/documentation

Developer

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Robert Friberg et al

Qdrant

Sybase, SAP

Initial release

2019

1995

2009

under the name LiveDB

2021

1993

Current release

cloud service with continuous releases

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

commercial

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

Rust

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Docker
Linux
macOS
Windows

Linux
Windows

Data scheme

Fixed schema with schema-less datatypes (dynamic)

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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

yes

User defined using .NET types and collections

Numbers, Strings, Geo, Boolean

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

can be achieved using .NET

Secondary indexes

all fields are automatically indexed

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP API
LINQ

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

.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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Delphi
Perl
PHP

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

yes

Triggers

yes

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

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

client side managed; servers are not synchronized

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Multi-source replication
Source-replica replication

Source-replica replication

Collection-level replication

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency, tunable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

depending on model

yes

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

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

caching of (temporary) tables can be configured

User concepts

Access control

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

Role based authorization

Key-based authentication

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.