Fixed cadence to seconds: making ClickHouse Cloud autoscaling more reactive

T1Covered by 1 source · first reported by Databricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale at 04 Aug, 13:19 UTC

How we rebuilt ClickHouse Cloud's autoscaling orchestration on Kubernetes' controller-runtime and a ClickHouse-powered signals table, adding a reactive fast path that scales services up in seconds instead of waiting for the next scheduled pass.

clouddev

Sources

• T1Fixed cadence to seconds: making ClickHouse Cloud autoscaling more reactiveDatabricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale04 Aug, 13:19