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.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	0.10
Rank	#358	Overall
	#48	Document stores
	#38	Graph DBMS
	#52	Key-value stores
	#35	Time Series DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Website

alasql.org

arcadedb.com

www.esgyn.cn

azure.microsoft.com/services/data-explorer

Technical documentation

github.com/AlaSQL/alasql

docs.arcadedb.com

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

Developer

Andrey Gershun & Mathias R. Wulff

Arcade Data

Esgyn

Microsoft

Initial release

2014

2021

2015

2019

Current release

September 2021

cloud service with continuous releases

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2.0

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

JavaScript

Java

C++, Java

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

All OS with a Java VM

Linux

hosted

Data scheme

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

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

SQL-like query language, no joins

yes

Kusto Query Language (KQL), SQL subset

APIs and other access methods

JavaScript API

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

ADO.NET
JDBC
ODBC

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

Supported programming languages

JavaScript

Java

All languages supporting JDBC/ODBC/ADO.Net

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

Server-side scripts

Stored procedures

Java Stored Procedures

Yes, possible languages: KQL, Python, R

Triggers

yes

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

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication between multi datacenters

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

none

Immediate Consistency

Eventual 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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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

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

Recent citations in the news

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

Create a Marvel Database with SQL and Javascript, the easy way
2 July 2019, Towards Data Science

Multi faceted data exploration in the browser using Leaflet and amCharts
3 May 2020, Towards Data Science

provided by Google News

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

Update records in a Kusto Database (public preview) | Azure updates
20 February 2024, azure.microsoft.com

Public Preview: Azure Data Explorer connector for Apache Flink | Azure updates
8 January 2024, azure.microsoft.com

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

New Features for graph-match KQL Operator: Enhanced Pattern Matching and Cycle Control | Azure updates
24 January 2024, azure.microsoft.com

provided by Google News

Share this page