DBMS > Apache Phoenix vs. ClickHouse vs. Derby vs. Microsoft Azure Data Explorer vs. Yanza

System Properties Comparison Apache Phoenix vs. ClickHouse vs. Derby vs. Microsoft Azure Data Explorer vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Fully managed big data interactive analytics platform

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

column oriented

Time Series DBMS

Secondary database models

Time Series DBMS

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

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	4.71
Rank	#69	Overall
	#37	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Website

phoenix.apache.org

clickhouse.com

db.apache.org/derby

azure.microsoft.com/services/data-explorer

yanza.com

Technical documentation

phoenix.apache.org

clickhouse.com/docs

db.apache.org/derby/manuals/index.html

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

Developer

Apache Software Foundation

Clickhouse Inc.

Apache Software Foundation

Microsoft

Yanza

Initial release

2014

2016

1997

2019

2015

Current release

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

v24.4.1.2088-stable, May 2024

10.17.1.0, November 2023

cloud service with continuous releases

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Apache version 2

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.

Implementation language

Java

C++

Java

Server operating systems

Linux
Unix
Windows

FreeBSD
Linux
macOS

All OS with a Java VM

hosted

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

Fixed schema with schema-less datatypes (dynamic)

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

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

SQL

Support of SQL

yes

Close to ANSI SQL (SQL/JSON + extensions)

yes

Kusto Query Language (KQL), SQL subset

APIs and other access methods

JDBC

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

JDBC

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

HTTP API

Supported programming languages

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

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

Java

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

yes

Java Stored Procedures

Yes, possible languages: KQL, Python, R

Triggers

yes

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

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

Source-replica replication

yes

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

fine grained access rights according to SQL-standard

Azure Active Directory Authentication

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.