DBMS > ClickHouse vs. Geode vs. PouchDB vs. RethinkDB vs. SQLite

System Properties Comparison ClickHouse vs. Geode vs. PouchDB vs. RethinkDB vs. SQLite

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

JavaScript DBMS with an API inspired by CouchDB

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Time Series DBMS

Spatial DBMS

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

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	2.74
Rank	#105	Overall
	#19	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

clickhouse.com/docs

geode.apache.org/docs

pouchdb.com/guides

rethinkdb.com/docs

www.sqlite.org/docs.html

Developer

Clickhouse Inc.

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

Apache Software Foundation

The Linux Foundation

since July 2017

Dwayne Richard Hipp

Initial release

2016

2002

2012

2009

2000

Current release

v24.4.1.2088-stable, May 2024

1.1, February 2017

7.1.1, June 2019

2.4.1, August 2020

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2

Open Source

Public Domain

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

C++

Java

JavaScript

C++

Server operating systems

FreeBSD
Linux
macOS

All OS with a Java VM

the JDK (8 or later) is also required

server-less, requires a JavaScript environment (browser, Node.js)

Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

yes

not rigid because of 'dynamic typing' concept.

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

via views

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language (OQL)

yes

SQL-92 is not fully supported

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

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

JavaScript

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

View functions in JavaScript

Triggers

yes

Cache Event Listeners

yes

Client-side triggers through changefeeds

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

range based

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

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Source-replica replication

none

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

yes

via file-system locks

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

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.

Access rights per client and object definable

yes

users and table-level permissions

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.