DBMS > Apache Drill vs. ClickHouse vs. H2 vs. MySQL vs. Riak TS

System Properties Comparison Apache Drill vs. ClickHouse vs. H2 vs. MySQL vs. Riak TS

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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.

Widely used open source RDBMS

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Time Series DBMS

Spatial DBMS

Document store
Spatial DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

Technical documentation

drill.apache.org/docs

clickhouse.com/docs

www.h2database.com/html/main.html

dev.mysql.com/doc

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Apache Software Foundation

Clickhouse Inc.

Thomas Mueller

Oracle

since 2010, originally MySQL AB, then Sun

Open Source, formerly Basho Technologies

Initial release

2012

2016

2005

1995

2015

Current release

1.20.3, January 2023

v24.4.1.2088-stable, May 2024

2.2.220, July 2023

8.4.0, April 2024

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

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

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

Erlang

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
macOS

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X

Data scheme

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.

yes

Secondary indexes

yes

restricted

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

Close to ANSI SQL (SQL/JSON + extensions)

yes

with proprietary extensions

yes, limited

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Native Erlang Interface

Supported programming languages

C++

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

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

yes

Java Stored Procedures and User-Defined Functions

yes

proprietary syntax

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

With clustering: 2 database servers on different computers operate on identical copies of a database

Multi-source replication
Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

links between datasets can be stored

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

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

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.