DBMS > Apache Drill vs. ClickHouse vs. etcd vs. HarperDB

System Properties Comparison Apache Drill vs. ClickHouse vs. etcd vs. HarperDB

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.

A distributed reliable key-value store

HarperDB takes the "stack" out of "tech stack" by combining an ultra-fast document-style data store, in-memory cache, real-time message broker, and your application components into a single distributed technology.

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

Document store

Secondary database models

Time Series DBMS

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

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	15.88
Rank	#37	Overall
	#22	Relational DBMS

Score	7.05
Rank	#53	Overall
	#5	Key-value stores

Score	0.55
Rank	#243	Overall
	#38	Document stores

Website

drill.apache.org

clickhouse.com

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

www.harperdb.io

Technical documentation

drill.apache.org/docs

clickhouse.com/docs

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

docs.harperdb.io/docs

Developer

Apache Software Foundation

Clickhouse Inc.

HarperDB

Initial release

2012

2016

2017

Current release

1.20.3, January 2023

v24.6.2.17-stable, July 2024

3.4, August 2019

3.1, August 2021

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

Open Source

Apache Version 2.0

commercial

free community edition available

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.

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

Node.js

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
macOS

FreeBSD
Linux
Windows

experimental

Linux
OS X

Data scheme

schema-free

yes

schema-free

dynamic schema

Typing

predefined data types such as float or date

yes

JSON data types

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)

SQL-like data manipulation statements

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

gRPC
JSON over HTTP

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

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
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

Server-side scripts

Stored procedures

user defined functions

yes

Custom Functions

since release 3.1

Triggers

yes, watching key changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

A table resides as a whole on one (or more) nodes in a cluster

Replication methods

Methods for redundantly storing data on multiple nodes

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.

yes

the nodes on which a table resides can be defined

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

Atomic execution of specific operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

yes, using LMDB

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 rights for users and 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.