DBMS > Amazon Redshift vs. ClickHouse vs. OpenTSDB

System Properties Comparison Amazon Redshift vs. ClickHouse vs. OpenTSDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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.

Scalable Time Series DBMS based on HBase

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Time Series DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	16.20
Rank	#37	Overall
	#23	Relational DBMS

Score	1.73
Rank	#147	Overall
	#12	Time Series DBMS

Website

aws.amazon.com/redshift

clickhouse.com

opentsdb.net

Technical documentation

docs.aws.amazon.com/redshift

clickhouse.com/docs

opentsdb.net/docs/build/html/index.html

Developer

Amazon (based on PostgreSQL)

Clickhouse Inc.

currently maintained by Yahoo and other contributors

Initial release

2012

2016

2011

Current release

v24.3.2.23-lts, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

LGPL

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.

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

Implementation language

C++

Java

Server operating systems

hosted

FreeBSD
Linux
macOS

Linux
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

Close to ANSI SQL (SQL/JSON + extensions)

APIs and other access methods

JDBC
ODBC

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

HTTP API
Telnet API

Supported programming languages

All languages supporting JDBC/ODBC

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

Erlang
Go
Java
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

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

fine grained access rights according to SQL-standard

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.

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.