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.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#19	Object oriented DBMS

Website

www.geomesa.org

machbase.com

azure.microsoft.com/services/data-explorer

origodb.com

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

machbase.com/dbms

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

origodb.com/docs

Developer

CCRi and others

Machbase

Microsoft

Robert Friberg et al

Initial release

2014

2013

2019

2009

under the name LiveDB

Current release

5.0.0, May 2024

V8.0, August 2023

cloud service with continuous releases

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free test version available

commercial

Open Source

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

Scala

Server operating systems

Linux
macOS
Windows

hosted

Linux
Windows

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

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

User defined using .NET types and collections

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

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

Kusto Query Language (KQL), SQL subset

APIs and other access methods

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

.NET Client API
HTTP API
LINQ

Supported programming languages

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

.Net

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

yes

Triggers

yes

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

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

selectable replication factor

yes

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

Source-replica replication

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

depending on storage layer

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

Write ahead log

In-memory capabilities

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

depending on storage layer

yes

volatile and lookup table

yes

User concepts

Access control

yes

depending on the DBMS used for storage

simple password-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

We’re retiring Azure Time Series Insights on 7 July 2024 – transition to Azure Data Explorer | Azure updates
31 May 2024, Microsoft

Update records in a Kusto Database (public preview) | Azure updates
20 February 2024, Microsoft

Public Preview: Azure Data Explorer connector for Apache Flink | Azure updates
8 January 2024, Microsoft

Announcing General Availability to migrate Virtual Network injected Azure Data Explorer Cluster to Private Endpoints ...
5 February 2024, Microsoft

Migration of Azure Virtual Network injected Azure Data Explorer cluster to Private Endpoints | Azure updates
4 December 2023, Microsoft

provided by Google News

Share this page