29 engineers on Hacker News describe using ClickHouse first-hand: 16 endorse it, 2 regret it, 0 are mixed.
“we switched from Druid+postgres+trino to just one big clickhouse node and I've never looked back.”
endorse · production · mial · 2026-06-20 · source ↗ · wrong label?“before we switched to clickhouse and it was night and day.”
endorse · production · dirtbag__dad · 2026-02-27 · source ↗ · wrong label?“the migration DX was a big challenge. Some migrations need to copy/reorder data between tables which can take a long time”
regret · production · marcklingen · 2024-12-27 · source ↗ · wrong label?“At my previous job (Cloudflare), we migrated from Elasticsearch to ClickHouse and saved nearly 10x reduction in data size and got 5x perf improvement.”
endorse · production · pradeepchhetri · 2024-07-22 · source ↗ · wrong label?“I traded ELK for Clickhouse & we use Fluentbit to relay logs”
endorse · production · aguacaterojo · 2024-02-06 · source ↗ · wrong label?“We switched to Clickhouse and have scaled 10.000x+ since with almost no issues.”
endorse · production · mxstbr · 2023-10-01 · source ↗ · wrong label?“this error-service I'm talking about is built on top of the ClickHouse, so it's quite responsive regardless of the large volumes of data.”
endorse · production · ekiauhce · 2022-12-27 · source ↗ · wrong label?“I've been using clickhouse-local (the CLI tool, not the database) a lot recently to do data analysis work.”
endorse · personal · justindeguzman · 2022-12-20 · source ↗ · wrong label?“we run MySQL, ClickHouse, and Prometheus to manage our own SaaS platform for ClickHouse. We are happy with the result.”
endorse · production · hodgesrm · 2022-10-16 · source ↗ · wrong label?“We run ClickHouse clusters in AWS / GCS using block storage in our cloud platform.”
endorse · production · hodgesrm · 2022-08-22 · source ↗ · wrong label?“At work we run a small CH cluster ( 10 TB+ Data ) and the functions for Working with JSON consume too much CPU resources.”
regret · production · ing33k · 2022-08-18 · source ↗ · wrong label?“So far we've been scaling by adding more compute since CH scales pretty well horizontally.”
endorse · production · flurly · 2022-08-18 · source ↗ · wrong label?“we migrated to a single ClickHouse or Postgres instance and got equivalent or better performance for a fraction of the economic and operational overhead.”
endorse · production · FridgeSeal · 2022-01-22 · source ↗ · wrong label?“ClickHouse handles data corruption surprisingly good - even if there are broken parts CH continues to serve the rest of data.”
endorse · production · vmihailenco · 2021-12-28 · source ↗ · wrong label?“We run almost all of our DBs - pg, cockroachdb, clickhouse ... Works really well.”
endorse · production · dilyevsky · 2021-07-28 · source ↗ · wrong label?“At Sematext we replaced our HBase based metrics datastore with Clickhouse. We are happy with the performance gain and flexibility.”
endorse · production · avisk · 2020-01-07 · source ↗ · wrong label?“I've been extremely impressed with its performance.”
endorse · personal · IanCal · 2018-11-30 · source ↗ · wrong label?“By comparison to Toku or RocksDB, Clickhouse is refreshingly well-documented and its easy for us to make consistent backups”
endorse · production · sethhochberg · 2018-09-20 · source ↗ · wrong label?“Now we've run into near-real-time requirements so clickhouse is getting thrown into the mix.”
neutral · production · efxhoy · 2026-08-19 · source ↗ · wrong label?“I work on a dashboarding / BI solution that is also built around markdown and clickhouse.”
neutral · production · amcaskill · 2026-04-18 · source ↗ · wrong label?“We have clickhouse, spark, trino/dremio, starrocks, druid, apache drill, and apache datafusion.”
neutral · production · Epa095 · 2024-12-22 · source ↗ · wrong label?“We use ClickHouse for time series data.”
neutral · production · osigurdson · 2024-12-07 · source ↗ · wrong label?“in prod, we just switch to our mysql, clickhouse, redis etc cluster”
neutral · production · anonzzzies · 2024-09-25 · source ↗ · wrong label?“We moved to running Clickhouse on EKS with EBS volumes for storage.”
neutral · production · ianburrell · 2024-02-20 · source ↗ · wrong label?“we run ClickHouse with Keeper for all of our server tests.”
neutral · production · antonio2368 · 2023-09-27 · source ↗ · wrong label?“We deal with payloads that are just a little too big for a database (we run Postgres and Clickhouse)”
neutral · production · tnolet · 2022-07-28 · source ↗ · wrong label?“we eventually offloaded a lot of aggregation tables to Clickhouse and turned the whole thing into a warehouse”
neutral · production · manish_gill · 2022-04-25 · source ↗ · wrong label?“we ran ClickHouse+ZK in the cloud”
neutral · production · vulkoingim · 2021-05-17 · source ↗ · wrong label?“We run our own analytics solution based on a js library, a small go app and ClickHouse for data aggregation.”
neutral · production · pachico · 2020-06-18 · source ↗ · wrong label?