Setting the file. One moment.
Chapter 03 · Clickhouse Architecture Advisor
Subchapter 3.9
rules/decision-ingestion-strategy.mdMarkdown2 KBView on GitHub
Do not recommend a single ingestion pattern for every workload. The right approach depends on:
| Condition | Recommended path | Category |
|---|---|---|
| Producers can batch to 10K-100K rows and latency tolerance is moderate | Direct inserts | official |
| Producers send many small inserts and cannot batch effectively | Async inserts | official |
| Producers are bursty, many independent writers exist, or decoupling is needed | Kafka engine + materialized view | derived |
| Reliability, replay, and ingestion fan-out are primary concerns | Upstream queue or log broker before ClickHouse | field |
Use when the application can naturally batch inserts into healthy sizes.
Why The existing best-practices guidance already favors appropriately sized insert batches.
Official sources
Use when producers emit many small writes and the application cannot easily batch.
Why Async inserts let ClickHouse buffer small writes server-side to reduce part pressure.
Official sources
Use when a queue-based, decoupled ingest path is needed.
Why This is typically the right design when multiple producers, burst handling, or replayability matter.
Category derived
Sources