DBMS > ClickHouse vs. Graph Engine vs. PouchDB vs. Riak KV vs. Solr

System Properties Comparison ClickHouse vs. Graph Engine vs. PouchDB vs. Riak KV vs. Solr

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 distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

JavaScript DBMS with an API inspired by CouchDB

Distributed, fault tolerant key-value store

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Document store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Search engine

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	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

Technical documentation

clickhouse.com/docs

www.graphengine.io/docs/manual

pouchdb.com/guides

www.tiot.jp/riak-docs/riak/kv/latest

solr.apache.org/resources.html

Developer

Clickhouse Inc.

Microsoft

Apache Software Foundation

OpenSource, formerly Basho Technologies

Apache Software Foundation

Initial release

2016

2010

2012

2009

2006

Current release

v24.4.1.2088-stable, May 2024

7.1.1, June 2019

3.2.0, December 2022

9.6.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

MIT License

Open Source

Apache version 2, commercial enterprise edition

Open Source

Apache Version 2

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

Implementation language

C++

.NET and C

JavaScript

Erlang

Java

Server operating systems

FreeBSD
Linux
macOS

.NET

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

Linux
OS X

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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 views

restricted

yes

All search fields are automatically indexed

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

Solr Parallel SQL Interface

APIs and other access methods

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

RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

HTTP API
Native Erlang Interface

Java API
RESTful HTTP/JSON 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

C#
C++
F#
Visual Basic

JavaScript

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

View functions in JavaScript

Erlang

Java plugins

Triggers

yes

pre-commit hooks and post-commit hooks

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

horizontal partitioning

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

no "single point of failure"

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

also with CouchDB databases
Source-replica replication

also with CouchDB databases

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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.

yes, using Riak Security

yes

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.