DBMS > ClickHouse vs. Ehcache vs. GeoMesa vs. Heroic vs. Microsoft Azure Data Explorer

System Properties Comparison ClickHouse vs. Ehcache vs. GeoMesa vs. Heroic vs. Microsoft Azure Data Explorer

Editorial information provided by DB-Engines

Name

Description

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 widely adopted Java cache with tiered storage options

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Fully managed big data interactive analytics platform

Primary database model

column oriented

Secondary database models

Time Series DBMS

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Website

clickhouse.com

www.ehcache.org

www.geomesa.org

github.com/spotify/heroic

azure.microsoft.com/services/data-explorer

Technical documentation

clickhouse.com/docs

www.ehcache.org/documentation

www.geomesa.org/documentation/stable/user/index.html

spotify.github.io/heroic

docs.microsoft.com/en-us/azure/data-explorer

Developer

Clickhouse Inc.

Terracotta Inc, owned by Software AG

CCRi and others

Spotify

Microsoft

Initial release

2016

2009

2014

2019

Current release

v24.4.1.2088-stable, May 2024

3.10.0, March 2022

5.0.0, May 2024

cloud service with continuous releases

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache License 2.0

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.

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.

Implementation language

C++

Java

Scala

Java

Server operating systems

FreeBSD
Linux
macOS

All OS with a Java VM

hosted

Data scheme

yes

schema-free

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-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.

yes

Secondary indexes

yes

via Elasticsearch

all fields are automatically indexed

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

Kusto Query Language (KQL), SQL subset

APIs and other access methods

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

JCache

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

Supported programming languages

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

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

Server-side scripts

Stored procedures

yes

Yes, possible languages: KQL, Python, R

Triggers

yes

Cache Event Listeners

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

by using Terracotta Server

depending on storage layer

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes

by using Terracotta Server

depending on storage layer

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

depending on storage layer

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

supports JTA and can work as an XA resource

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

depending on storage layer

User concepts

Access control

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.

yes

depending on the DBMS used for storage

Azure Active Directory Authentication

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.