DBMS > Google Cloud Bigtable vs. Microsoft Azure Data Explorer vs. MySQL vs. XTDB

System Properties Comparison Google Cloud Bigtable vs. Microsoft Azure Data Explorer vs. MySQL vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Fully managed big data interactive analytics platform

Widely used open source RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store
Wide column store

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Document store

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

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

Score	2.97
Rank	#92	Overall
	#15	Key-value stores
	#8	Wide column stores

Score	3.28
Rank	#83	Overall
	#45	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

cloud.google.com/bigtable

azure.microsoft.com/services/data-explorer

www.mysql.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

cloud.google.com/bigtable/docs

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

dev.mysql.com/doc

www.xtdb.com/docs

Developer

Google

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Juxt Ltd.

Initial release

2015

2019

1995

2019

Current release

cloud service with continuous releases

9.0.0, July 2024

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MIT License

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 C++

Clojure

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

schema-free

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

yes, extensible-data-notation format

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

all fields are automatically indexed

yes

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

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

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
JDBC

Supported programming languages

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

.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

Clojure
Java

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

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

Multi-source replication
Source-replica replication

yes, each node contains all data

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 (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-row operations

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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 rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Azure Active Directory Authentication

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.