DBMS > Apache Impala vs. ClickHouse vs. EventStoreDB

System Properties Comparison Apache Impala vs. ClickHouse vs. EventStoreDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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.

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Primary database model

Relational DBMS

Event Store

Secondary database models

Document store

Time Series DBMS

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

Score	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	16.20
Rank	#37	Overall
	#23	Relational DBMS

Score	1.14
Rank	#181	Overall
	#1	Event Stores

Website

impala.apache.org

clickhouse.com

www.eventstore.com

Technical documentation

impala.apache.org/impala-docs.html

clickhouse.com/docs

developers.eventstore.com

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Clickhouse Inc.

Event Store Limited

Initial release

2013

2016

2012

Current release

4.1.0, June 2022

v23.12.1.1368-stable, December 2023

21.2, February 2021

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

Open Source

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 Clickhouse: Managed cloud data warehousing with high-speed analytics.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
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

C++

Server operating systems

Linux

FreeBSD
Linux
macOS

Linux
Windows

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

Close to ANSI SQL (SQL/JSON + extensions)

APIs and other access methods

JDBC
ODBC

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

Supported programming languages

All languages supporting JDBC/ODBC

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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 rights for users, groups and roles

based on Apache Sentry and Kerberos

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.

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.