DBMS > ClickHouse vs. CouchDB vs. Faircom EDGE vs. OrigoDB vs. RDF4J

System Properties Comparison ClickHouse vs. CouchDB vs. Faircom EDGE vs. OrigoDB vs. RDF4J

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 native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

A fully ACID in-memory object graph database

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Relational DBMS

Document store

Key-value store
Relational DBMS

Document store
Object oriented DBMS

RDF store

Secondary database models

Time Series DBMS

Spatial DBMS

using the Geocouch extension

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

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

clickhouse.com

couchdb.apache.org

www.faircom.com/products/faircom-edge

origodb.com

rdf4j.org

Technical documentation

clickhouse.com/docs

docs.couchdb.org/en/stable

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

origodb.com/docs

rdf4j.org/documentation

Developer

Clickhouse Inc.

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

FairCom Corporation

Robert Friberg et al

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2016

2005

1979

2009

under the name LiveDB

2004

Current release

v24.4.1.2088-stable, May 2024

3.3.3, December 2023

V3, October 2020

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache version 2

commercial

Restricted, free version available

Open Source

Eclipse Distribution License (EDL), v1.0.

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

Erlang

ANSI C, C++

Java

Server operating systems

FreeBSD
Linux
macOS

Android
BSD
Linux
OS X
Solaris
Windows

Android
Linux

ARM, x86
Raspbian
Windows

Linux
Windows

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

yes

RDF Schemas

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

via views

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

ANSI SQL queries

APIs and other access methods

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

RESTful HTTP/JSON API

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

.NET Client API
HTTP API
LINQ

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

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#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

.Net

Java
PHP
Python

Server-side scripts

Stored procedures

yes

View functions in JavaScript

yes

.Net, JavaScript, C/C++

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

improved architecture with release 2.0

File partitioning

Customizable business rules for partitioning

horizontal partitioning

client side managed; servers are not synchronized

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

yes

Synchronous and asynchronous realtime replication based on transaction logs

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
Tunable Consistency

Foreign keys

Referential integrity

yes

when using SQL

depending on model

Transaction concepts

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

atomic operations within a single document possible

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

across SQL and NoSQL

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

in-memory storage is supported as well

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 for users can be defined per database

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Role based authorization

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.