DBMS > Apache Phoenix vs. MySQL vs. Prometheus vs. YugabyteDB

System Properties Comparison Apache Phoenix vs. MySQL vs. Prometheus vs. YugabyteDB

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

Widely used open source RDBMS

Open-source Time Series DBMS and monitoring system

High-performance distributed SQL database for global, internet-scale applications. Wire and feature compatible with PostgreSQL.

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Wide column store

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	2.91
Rank	#102	Overall
	#51	Relational DBMS

Website

Technical documentation

phoenix.apache.org

dev.mysql.com/doc

prometheus.io/docs

docs.yugabyte.com
github.com/yugabyte/yugabyte-db

Developer

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Yugabyte Inc.

Initial release

2014

1995

2015

2017

Current release

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

8.4.0, April 2024

2.19, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

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.

YugabyteDB Managed is the fully managed database-as-a-service offering of YugabyteDB. Get started quickly, and effortlessly ensure continuous availability and limitless scale of your cloud native applications.

Implementation language

Java

C and C++

Server operating systems

Linux
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Linux
OS X

Data scheme

yes

late-bound, schema-on-read capabilities

yes

depending on used data model

Typing

predefined data types such as float or date

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes, PostgreSQL compatible

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP/JSON API

JDBC
YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language
YSQL - a fully relational SQL API that is wire compatible with the SQL language in PostgreSQL

Supported programming languages

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

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust
Scala

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

yes

sql, plpgsql, C

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Hash and Range Sharding, row-level geo-partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

by Federation

Based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability

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

none

Strong consistency on writes and tunable consistency on reads

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture.

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

based on RocksDB

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

no user groups or roles

yes

More information provided by the system vendor

Specific characteristics

YugabyteDB is an open source distributed SQL database for cloud native transactional...
» more

Competitive advantages

PostgreSQL compatible: Get instantly productive with a PostgreSQL compatible RDBMS....
» more

Typical application scenarios

Systems of record and engagement for cloud native applications that require resilience,...
» more

Market metrics

2 Million+ lifetime clusters deployed, 6.5K+ GitHub stars, 7K YugabyteDB Community...
» more

Licensing and pricing models

Apache 2.0 license for the database
» 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.