DBMS > ClickHouse vs. Fauna vs. Geode vs. SingleStore vs. XTDB

System Properties Comparison ClickHouse vs. Fauna vs. Geode vs. SingleStore vs. XTDB

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.

Fauna provides a web-native interface, with support for GraphQL and custom business logic that integrates seamlessly with the rest of the serverless ecosystem. The underlying globally distributed storage and compute platform is fast, consistent, and reliable, with a modern security infrastructure.

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Key-value store

Relational DBMS

Document store

Secondary database models

Time Series DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	15.88
Rank	#37	Overall
	#22	Relational DBMS

Score	1.55
Rank	#143	Overall
	#26	Document stores
	#13	Graph DBMS
	#66	Relational DBMS
	#13	Time Series DBMS

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

clickhouse.com/docs

docs.fauna.com

geode.apache.org/docs

docs.singlestore.com

www.xtdb.com/docs

Developer

Clickhouse Inc.

Fauna, Inc.

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

SingleStore Inc.

Juxt Ltd.

Initial release

2016

2014

2002

2013

2019

Current release

v24.6.2.17-stable, July 2024

1.1, February 2017

8.5, January 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free developer edition available

Open Source

MIT License

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

Implementation language

C++

Scala

Java

C++, Go

Clojure

Server operating systems

FreeBSD
Linux
macOS

hosted

All OS with a Java VM

the JDK (8 or later) is also required

Linux

64 bit version required

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language (OQL)

yes

but no triggers and foreign keys

limited SQL, making use of Apache Calcite

APIs and other access methods

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

RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

HTTP REST
JDBC

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

C#
Go
Java
JavaScript
Python
Ruby
Scala
Swift

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

Bash
C
C#
Java
JavaScript (Node.js)
Python

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

key based and custom

horizontal partitioning

consistent hashing

Sharding

hash partitioning

none

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

Source-replica replication

stores two copies of each physical data partition on two separate nodes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

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.

Identity management, authentication, and access control

Access rights per client and object definable

Fine grained access control via users, groups 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.