DBMS > Apache Impala vs. ClickHouse vs. Elasticsearch vs. Google Cloud Spanner vs. MySQL

System Properties Comparison Apache Impala vs. ClickHouse vs. Elasticsearch vs. Google Cloud Spanner vs. MySQL

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.

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

Widely used open source RDBMS

Primary database model

Relational DBMS

Search engine

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

Time Series DBMS

Document store
Spatial DBMS
Vector DBMS

Document store
Spatial 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	134.78
Rank	#7	Overall
	#1	Search engines

Score	2.89
Rank	#105	Overall
	#53	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Website

impala.apache.org

clickhouse.com

www.elastic.co/elasticsearch

cloud.google.com/spanner

www.mysql.com

Technical documentation

impala.apache.org/impala-docs.html

clickhouse.com/docs

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

cloud.google.com/spanner/docs

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Clickhouse Inc.

Elastic

Google

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2016

2010

2017

1995

Current release

4.1.0, June 2022

v23.12.1.1368-stable, December 2023

8.6, January 2023

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

Open Source

Elastic License

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

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.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

Java

C and C++

Server operating systems

Linux

FreeBSD
Linux
macOS

All OS with a Java VM

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like DML and DDL statements

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language

yes

Query statements complying to ANSI 2011

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

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

Java API
RESTful HTTP/JSON API

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

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

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

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.

yes

Multi-source replication with 3 replicas for regional instances.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

ES-Hadoop Connector

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Strict serializable isolation

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Memcached and Redis integration

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.

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users with fine-grained authorization concept

no user groups or roles

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.