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	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	4.67
Rank	#77	Overall
	#42	Relational DBMS

Score	5.16
Rank	#69	Overall
	#37	Relational DBMS

Website

cloud.google.com/bigquery

hazelcast.com

www.actian.com/databases/ingres

azure.microsoft.com/services/data-explorer

Technical documentation

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

docs.actian.com/ingres

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

Developer

Google

Hazelcast

Actian Corporation

Microsoft

Initial release

2010

2008

1974

originally developed at University Berkely in early 1970s

2019

Current release

5.3.6, November 2023

11.2, May 2022

cloud service with continuous releases

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

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.

Implementation language

Java

Server operating systems

hosted

All OS with a Java VM

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

yes

schema-free

yes

Fixed schema with schema-less datatypes (dynamic)

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

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

the object must implement a serialization strategy

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

SQL-like query language

yes

Kusto Query Language (KQL), SQL subset

APIs and other access methods

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

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

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

yes

Yes, possible languages: KQL, Python, R

Triggers

yes

Events

yes

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

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Ingres Replicator

yes

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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.

yes

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Role-based access control

fine grained access rights according to SQL-standard

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.