DBMS > Apache Phoenix vs. ClickHouse vs. etcd vs. Google Cloud Firestore vs. OpenEdge

System Properties Comparison Apache Phoenix vs. ClickHouse vs. etcd vs. Google Cloud Firestore vs. OpenEdge

Editorial information provided by DB-Engines

Name

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.

A distributed reliable key-value store

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Application development environment with integrated database management system

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	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Website

phoenix.apache.org

clickhouse.com

etcd.io
github.com/etcd-io/etcd

firebase.google.com/products/firestore

www.progress.com/openedge

Technical documentation

phoenix.apache.org

clickhouse.com/docs

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

firebase.google.com/docs/firestore

documentation.progress.com/output/ua/OpenEdge_latest

Developer

Apache Software Foundation

Clickhouse Inc.

Google

Progress Software Corporation

Initial release

2014

2016

2017

1984

Current release

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

v24.4.1.2088-stable, May 2024

3.4, August 2019

OpenEdge 12.2, March 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Apache Version 2.0

commercial

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.

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++

Server operating systems

Linux
Unix
Windows

FreeBSD
Linux
macOS

FreeBSD
Linux
Windows

experimental

hosted

AIX
HP-UX
Linux
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

Close to ANSI SQL (SQL/JSON + extensions)

yes

close to SQL 92

APIs and other access methods

JDBC

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

gRPC
JSON over HTTP

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

Progress proprietary ABL (Advanced Business Language)

Server-side scripts

Stored procedures

user defined functions

yes

yes, Firebase Rules & Cloud Functions

yes

Triggers

yes, watching key changes

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

Sharding

horizontal partitioning

since Version 11.4

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.

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

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

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

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.

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Users and groups

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.