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	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.00
Rank	#385	Overall
	#40	Graph DBMS

Score	3.28
Rank	#83	Overall
	#45	Relational DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Website

drill.apache.org

galaxybase.com

azure.microsoft.com/services/data-explorer

origodb.com

Technical documentation

drill.apache.org/docs

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

origodb.com/docs

Developer

Apache Software Foundation

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Microsoft

Robert Friberg et al

Initial release

2012

2017

2019

2009

under the name LiveDB

Current release

1.20.3, January 2023

Nov 20, November 2021

cloud service with continuous releases

License

Commercial or Open Source

Open Source

Apache Version 2

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

C and Java

Server operating systems

Linux
OS X
Windows

Linux

hosted

Linux
Windows

Data scheme

schema-free

Strong typed schema

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 SELECT statement is SQL:2003 compliant

Kusto Query Language (KQL), SQL subset

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

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

.NET Client API
HTTP API
LINQ

Supported programming languages

C++

Go
Java
Python

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

.Net

Server-side scripts

Stored procedures

user defined functions

user defined procedures and functions

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

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

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

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Depending on the underlying data source

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 the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Role-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

Recent citations in the news

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Analyse Kafka messages with SQL queries using Apache Drill
27 September 2019, Towards Data Science

MapR Advances Support for Flexible and High Performance Analytics on JSON and S3 Data with Apache Drill
30 January 2019, Business Wire

Apache Drill Adds New Data Formats
28 March 2022, iProgrammer

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

provided by Google News

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

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

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

Announcing General Availability of Graph Semantics in Kusto
27 May 2024, Microsoft

General availability: Azure Data Explorer adds new geospatial capabilities
23 January 2024, Microsoft

provided by Google News

Share this page