DBMS > Apache Druid vs. ClickHouse vs. Elasticsearch vs. Microsoft Access vs. TerarkDB

System Properties Comparison Apache Druid vs. ClickHouse vs. Elasticsearch vs. Microsoft Access vs. TerarkDB

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS
Time Series DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS
Vector DBMS

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

druid.apache.org

clickhouse.com

www.elastic.co/elasticsearch

www.microsoft.com/en-us/microsoft-365/access

github.com/bytedance/terarkdb

Technical documentation

druid.apache.org/docs/latest/design

clickhouse.com/docs

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

developer.microsoft.com/en-us/access

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation and contributors

Clickhouse Inc.

Elastic

Microsoft

ByteDance, originally Terark

Initial release

2012

2016

2010

1992

2016

Current release

29.0.1, April 2024

v24.4.1.2088-stable, May 2024

8.6, January 2023

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache 2.0

Open Source

Elastic License

commercial

Bundled with Microsoft Office

commercial

restricted open source version 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.

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.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.

Implementation language

Java

C++

Java

C++

Server operating systems

Linux
OS X
Unix

FreeBSD
Linux
macOS

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

Data scheme

yes

schema-less columns are supported

yes

schema-free

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

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.

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL for querying

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC
RESTful HTTP/JSON API

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

Java API
RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

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

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

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

C++
Java

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Triggers

yes

by using the 'percolation' feature

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

key based and custom

Sharding

none

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.

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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

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.

a simple user-level security was built in till version Access 2003

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.