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.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

github.com/graphite-project/graphite-web

azure.microsoft.com/services/data-explorer

rocksdb.org

vitess.io

Technical documentation

graphite.readthedocs.io

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

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

Chris Davis

Microsoft

Facebook, Inc.

The Linux Foundation, PlanetScale

Initial release

2006

2019

2013

Current release

cloud service with continuous releases

9.2.1, May 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

BSD

Open Source

Apache Version 2.0, commercial licenses 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

Python

C++

Server operating systems

Linux
Unix

hosted

Linux

Docker
Linux
macOS

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

schema-free

yes

Typing

predefined data types such as float or date

Numeric data only

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

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

APIs and other access methods

HTTP API
Sockets

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

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

JavaScript (Node.js)
Python

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

C
C++
Go
Java
Perl
Python
Ruby

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

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

Triggers

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

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

yes

Multi-source replication
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

none

Eventual Consistency
Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

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

User concepts

Access control

Azure Active Directory 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.