GoKawiilTinybird engineer details six years of running petabyte-scale ClickHouse clusters
A Tinybird engineer who has operated ClickHouse clusters since version 18.4 nearly six years ago published a detailed retrospective on running the database at petabyte scale. The post walks through the standard shard-and-replica architecture ClickHouse recommends and highlights the operational pitfalls that only surface once a cluster is running in production. Tinybird notes it is an independent contributor to the open-source project and unaffiliated with ClickHouse, Inc.
GoKawiil's interpretation of the reporting above, not reported fact.
Setting up ClickHouse is well documented, but few public accounts detail the long-term operational burden of keeping large clusters healthy, making this a useful real-world reference for teams evaluating the database. It also underscores how open-source infrastructure companies like Tinybird build expertise and credibility by contributing performance improvements back upstream while building commercial products around the technology.
- The author has run ClickHouse clusters at petabyte scale for nearly six years at Tinybird.
- Standard ClickHouse architecture relies on sharding data across buckets and replicating each shard.
- The real challenge in production ClickHouse deployments is long-term operational maintenance, not initial setup.
Source: tinybird.co, 2026-09-07
Published there as: “I've operated petabyte-scale ClickHouse clusters for 5 years”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.