DBMS > Microsoft Azure Data Explorer vs. MySQL vs. Rockset vs. SpatiaLite vs. Vitess

System Properties Comparison Microsoft Azure Data Explorer vs. MySQL vs. Rockset vs. SpatiaLite vs. Vitess

Editorial information provided by DB-Engines

Name

Description

Fully managed big data interactive analytics platform

Widely used open source RDBMS

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Spatial extension of SQLite

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Document store

Spatial DBMS

Relational DBMS

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

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

Document store
Spatial DBMS

Relational DBMS
Search engine

Relational DBMS

Document store
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

azure.microsoft.com/services/data-explorer

www.mysql.com

rockset.com

www.gaia-gis.it/fossil/libspatialite/index

vitess.io

Technical documentation

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

dev.mysql.com/doc

docs.rockset.com

www.gaia-gis.it/gaia-sins/spatialite_topics.html

vitess.io/docs

Developer

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Rockset

Alessandro Furieri

The Linux Foundation, PlanetScale

Initial release

2019

1995

2019

2008

2013

Current release

cloud service with continuous releases

8.4.0, April 2024

5.0.0, August 2020

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

Apache Version 2.0, commercial licenses available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

hosted

server-less

Docker
Linux
macOS

Data scheme

Fixed schema with schema-less datatypes (dynamic)

yes

schema-free

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

yes

dynamic typing

yes

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

ingestion from XML files supported

Secondary indexes

all fields are automatically indexed

yes

all fields are automatically indexed

yes

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

Read-only SQL queries, including JOINs

yes

with proprietary extensions

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Go
Java
JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

yes

proprietary syntax

Triggers

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Automatic sharding

none

Sharding

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.

Multi-source replication
Source-replica replication

yes

none

Multi-source replication
Source-replica replication

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
Immediate Consistency

Immediate Consistency

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

table locks or row locks depending on storage engine

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

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and organizations can be defined via Rockset console

Users with fine-grained authorization concept

no user groups or roles

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.