Setting the file. One moment.
Chapter 03 · Clickhouse Architecture Advisor
Subchapter 3.13
rules/decision-real-time-preaggregation.mdMarkdown2 KBView on GitHub
Real-time workloads should not be forced into either “everything raw” or “precompute everything.” The correct choice depends on freshness, query repetition, and transformation complexity.
| Condition | Recommendation | Category |
|---|---|---|
| Queries are ad hoc and freshness matters most | Query raw tables | derived |
| Repeated aggregation pattern over append-only data | Incremental MV | official |
| Complex joins or scheduled batch recomputation | Refreshable MV | official |
| Very hot dashboard or alerting path | Incremental rollup table plus raw table fallback | derived |
Why Incremental MVs are the documented best fit for continuously maintained rollups over insert streams.
Official sources
Why Refreshable MVs better fit complex transformations that do not need per-row trigger semantics.
Official sources
Why A raw table preserves flexibility while a rollup path protects latency-sensitive workloads.
Category derived
Official context