DBMS > Apache Phoenix vs. Databend vs. Microsoft Azure Table Storage vs. MySQL

System Properties Comparison Apache Phoenix vs. Databend vs. Microsoft Azure Table Storage vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

A Wide Column Store for rapid development using massive semi-structured datasets

Widely used open source RDBMS

Primary database model

Relational DBMS

Wide column store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	1.90
Rank	#125	Overall
	#59	Relational DBMS

Score	0.28
Rank	#287	Overall
	#131	Relational DBMS

Score	3.55
Rank	#80	Overall
	#6	Wide column stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

phoenix.apache.org

github.com/datafuselabs/databend
www.databend.com

azure.microsoft.com/en-us/services/storage/tables

www.mysql.com

Technical documentation

phoenix.apache.org

docs.databend.com

dev.mysql.com/doc

Developer

Apache Software Foundation

Databend Labs

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2021

2012

1995

Current release

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

1.0.59, April 2023

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

Implementation language

Java

Rust

C and C++

Server operating systems

Linux
Unix
Windows

hosted
Linux
macOS

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

JDBC

CLI Client
JDBC
RESTful HTTP API

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

Go
Java
JavaScript (Node.js)
Python
Rust

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

ACID

yes

optimistic locking

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Users with fine-grained authorization concept, user roles

Access rights based on private key authentication or shared access signatures

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.