DBMS > Apache Drill vs. ClickHouse vs. Google BigQuery

System Properties Comparison Apache Drill vs. ClickHouse vs. Google BigQuery

Please select another system to include it in the comparison.

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.

Large scale data warehouse service with append-only tables

Primary database model

Document store
Relational DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	16.20
Rank	#37	Overall
	#23	Relational DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Website

drill.apache.org

clickhouse.com

cloud.google.com/bigquery

Technical documentation

drill.apache.org/docs

clickhouse.com/docs

cloud.google.com/bigquery/docs

Developer

Apache Software Foundation

Clickhouse Inc.

Google

Initial release

2012

2016

2010

Current release

1.20.3, January 2023

v24.3.2.23-lts, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 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

C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
macOS

hosted

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

Close to ANSI SQL (SQL/JSON + extensions)

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

RESTful HTTP/JSON API

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

in JavaScript

Triggers

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

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

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.

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.