DBMS > ClickHouse vs. Geode vs. GeoMesa vs. Hazelcast

System Properties Comparison ClickHouse vs. Geode vs. GeoMesa vs. Hazelcast

Please select another system to include it in the comparison.

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.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

A widely adopted in-memory data grid

Primary database model

Secondary database models

Time Series DBMS

Document store

JSON support with IMDG 3.12

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

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Website

Technical documentation

clickhouse.com/docs

geode.apache.org/docs

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

hazelcast.org/imdg/docs

Developer

Clickhouse Inc.

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

CCRi and others

Hazelcast

Initial release

2016

2002

2014

2008

Current release

v24.4.1.2088-stable, May 2024

1.1, February 2017

5.0.0, May 2024

5.3.6, November 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache License 2.0

Open Source

Apache Version 2; commercial licenses 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.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

C++

Java

Scala

Java

Server operating systems

FreeBSD
Linux
macOS

All OS with a Java VM

the JDK (8 or later) is also required

All OS with a Java VM

Data scheme

yes

schema-free

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language (OQL)

SQL-like query language

APIs and other access methods

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

Java Client API
Memcached protocol
RESTful HTTP API

JCache
JPA
Memcached protocol
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

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Server-side scripts

Stored procedures

yes

user defined functions

yes

Event Listeners, Executor Services

Triggers

yes

Cache Event Listeners

yes

Events

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication

depending on storage layer

yes

Replicated Map

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

depending on storage layer

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

one or two-phase-commit; repeatable reads; read commited

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

yes

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.

Access rights per client and object definable

yes

depending on the DBMS used for storage

Role-based access control

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.