DBMS > Apache Phoenix vs. Microsoft Azure Data Explorer vs. MySQL vs. OpenEdge vs. TiDB

System Properties Comparison Apache Phoenix vs. Microsoft Azure Data Explorer vs. MySQL vs. OpenEdge vs. TiDB

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

Fully managed big data interactive analytics platform

Widely used open source RDBMS

Application development environment with integrated database management system

TiDB is an open source distributed SQL database that supports Hybrid Transactional/Analytical Processing (HTAP) workloads. It is MySQL compatible and features horizontal scalability, strong consistency, and high availability.

Primary database model

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

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

Document store

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	4.25
Rank	#74	Overall
	#40	Relational DBMS

Website

phoenix.apache.org

azure.microsoft.com/services/data-explorer

www.mysql.com

www.progress.com/openedge

pingcap.com

Technical documentation

phoenix.apache.org

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

dev.mysql.com/doc

documentation.progress.com/output/ua/OpenEdge_latest

docs.pingcap.com/tidb/stable

Developer

Apache Software Foundation

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Progress Software Corporation

PingCAP, Inc.

Initial release

2014

2019

1995

1984

2016

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

cloud service with continuous releases

8.4.0, April 2024

OpenEdge 12.2, March 2020

8.1.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

Apache 2.0

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.

TiDB Cloud: Fully-managed TiDB Service. Bring everything great about TiDB to the cloud.

Implementation language

Java

C and C++

Go, Rust

Server operating systems

Linux
Unix
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

yes

late-bound, schema-on-read capabilities

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

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

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

yes

close to SQL 92

yes

APIs and other access methods

JDBC

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

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

GORM
JDBC
ODBC
Proprietary protocol
SQLAlchemy

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.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

Progress proprietary ABL (Advanced Business Language)

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

user defined functions

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

yes

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

horizontal partitioning

since Version 11.4

horizontal partitioning (by key range)

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

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

Multi-source replication
Source-replica replication

Source-replica replication

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Spark connector (open source): github.com/Azure/azure-kusto-spark

yes

with TiSpark Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

full support since version 6.6

Transaction concepts

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

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

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

Users and groups

Fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

TiDB is an advanced open-source, distributed SQL database for modern application...
» more

Competitive advantages

- HORIZONTAL SCALING : TiDB grants total transparency into your data workloads without...
» more

Typical application scenarios

TiDB is ideal for transactional applications that require extreme scalability and...
» more

Key customers

Block, Pinterest, Catalyst, Bolt, Flipkart, Capcom, Shopee (E-commerce), JD Cloud...
» more

Market metrics

34K+ GitHub stars 5K+ members in TiDB Community Slack 1K+ community contributors...
» more

Licensing and pricing models

TiDB Community : Free open source software (Apache 2.0) TiDB Self-Hosted : Enterprise...
» more

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.