DBMS > ClickHouse vs. OpenQM vs. YottaDB

System Properties Comparison ClickHouse vs. OpenQM vs. YottaDB

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.

QpenQM is a high-performance, self-tuning, multi-value DBMS

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Multivalue DBMS

Key-value store

Secondary database models

Time Series DBMS

Relational DBMS

using the Octo plugin

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

Score	15.88
Rank	#37	Overall
	#22	Relational DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Score	0.21
Rank	#309	Overall
	#43	Key-value stores

Website

clickhouse.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

yottadb.com

Technical documentation

clickhouse.com/docs

yottadb.com/resources/documentation

Developer

Clickhouse Inc.

Rocket Software, originally Martin Phillips

YottaDB, LLC

Initial release

2016

1993

2001

Current release

v24.6.2.17-stable, July 2024

3.4-12

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPLv2, extended commercial license available

Open Source

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

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

Server operating systems

FreeBSD
Linux
macOS

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Docker
Linux

Data scheme

yes

with some exceptions

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

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

by using the Octo plugin

APIs and other access methods

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

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

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
Basic
C
Java
Objective C
PHP
Python

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

yes

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

optimistic locking

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

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 can be defined down to the item level

Users and groups based on OS-security mechanisms

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.