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

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

azure.microsoft.com/services/data-explorer

orientdb.org

www.snowflake.com

sphinxsearch.com

Technical documentation

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

www.orientdb.com/docs/last/index.html

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

Microsoft

OrientDB LTD; CallidusCloud; SAP

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

2019

2010

2014

2001

Current release

cloud service with continuous releases

3.2.29, March 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

Open Source

GPL version 2, commercial licence 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

C++

Server operating systems

hosted

All OS with a Java JDK (>= JDK 6)

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

Fixed schema with schema-less datatypes (dynamic)

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

support of semi-structured data formats (JSON, XML, Avro)

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

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

all fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

SQL-like query language, no joins

yes

SQL-like query language (SphinxQL)

APIs and other access methods

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

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

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

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

Java, Javascript

user defined functions

Triggers

yes

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

Hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

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

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

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

User concepts

Access control

Azure Active Directory Authentication

Access rights for users and roles; record level security configurable

Users with fine-grained authorization concept, user roles and pluggable 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.