DBMS > Apache Phoenix vs. ClickHouse vs. Firebase Realtime Database vs. Interbase vs. Yanza

System Properties Comparison Apache Phoenix vs. ClickHouse vs. Firebase Realtime Database vs. Interbase 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.

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Light-weight proven RDBMS

originally from Borland

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Time Series DBMS

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	14.29
Rank	#39	Overall
	#6	Document stores

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Website

phoenix.apache.org

clickhouse.com

firebase.google.com/products/realtime-database

www.embarcadero.com/products/interbase

yanza.com

Technical documentation

phoenix.apache.org

clickhouse.com/docs

firebase.google.com/docs/database

docs.embarcadero.com/products/interbase

Developer

Apache Software Foundation

Clickhouse Inc.

Google

acquired by Google 2014

Embarcadero

Yanza

Initial release

2014

2016

2012

1984

2015

Current release

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

v24.4.1.2088-stable, May 2024

InterBase 2020, December 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

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.

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.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.

Implementation language

Java

C++

Server operating systems

Linux
Unix
Windows

FreeBSD
Linux
macOS

hosted

Android
iOS
Linux
OS X
Windows

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

schema-free

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.

export as XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

Close to ANSI SQL (SQL/JSON + extensions)

yes

APIs and other access methods

JDBC

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

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC

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
JavaScript
Objective-C

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

yes

limited functionality with using 'rules'

yes

Interbase procedure and trigger language

Triggers

Callbacks are triggered when data changes

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

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.

Interbase Change Views

none

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

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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.

yes, based on authentication and database rules

fine grained access rights according to SQL-standard

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.