DBMS > Apache Druid vs. ClickHouse vs. HEAVY.AI vs. Tarantool

System Properties Comparison Apache Druid vs. ClickHouse vs. HEAVY.AI vs. Tarantool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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 high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Time Series DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

druid.apache.org

clickhouse.com

github.com/heavyai/heavydb
www.heavy.ai

www.tarantool.io

Technical documentation

druid.apache.org/docs/latest/design

clickhouse.com/docs

docs.heavy.ai

www.tarantool.io/en/doc

Developer

Apache Software Foundation and contributors

Clickhouse Inc.

HEAVY.AI, Inc.

Initial release

2012

2016

2008

Current release

29.0.1, April 2024

v24.3.2.23-lts, April 2024

5.10, January 2022

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache 2.0

Open Source

Apache Version 2; enterprise edition available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

Java

C++

C++ and CUDA

C and C++

Server operating systems

Linux
OS X
Unix

FreeBSD
Linux
macOS

Linux

BSD
Linux
macOS

Data scheme

yes

schema-less columns are supported

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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 for querying

Close to ANSI SQL (SQL/JSON + extensions)

yes

Full-featured ANSI SQL support

APIs and other access methods

JDBC
RESTful HTTP/JSON API

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

JDBC
ODBC
Thrift
Vega

Open binary protocol

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

All languages supporting JDBC/ODBC/Thrift
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

Lua, C and SQL stored procedures

Triggers

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

key based and custom

Sharding

Round robin

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

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

Multi-source replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.