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	0.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

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

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.ibm.com/products/db2-event-store

azure.microsoft.com/services/data-explorer

origodb.com

www.sqlite.org

Technical documentation

www.ibm.com/docs/en/db2-event-store

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

origodb.com/docs

www.sqlite.org/docs.html

Developer

IBM

Microsoft

Robert Friberg et al

Dwayne Richard Hipp

Initial release

2017

2019

2009

under the name LiveDB

2000

Current release

2.0

cloud service with continuous releases

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

free developer edition available

commercial

Open Source

Public Domain

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

C and C++

Server operating systems

Linux

Linux, macOS, Windows for the developer addition

hosted

Linux
Windows

server-less

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

yes

dynamic column types

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

User defined using .NET types and collections

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

yes

through the embedded Spark runtime

Kusto Query Language (KQL), SQL subset

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

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

.NET Client API
HTTP API
LINQ

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

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

.Net

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Yes, possible languages: KQL, Python, R

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

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

yes

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

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

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

No - written data is immutable

yes

via file-system locks

Durability

Support for making data persistent

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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

User concepts

Access control

fine grained access rights according to SQL-standard

Azure Active Directory Authentication

Role based authorization

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.