Why is an update-heavy workload hard for a data warehouse?
Warehouses are optimised for appending large batches and scanning columns. Frequent small updates to existing rows force expensive merges or rewrites of the files holding them. Content tools where users edit existing items far more than they create new ones hit this wall quickly, in both speed and cost.
Answered in
From Sharded Postgres to a Data Lake: CDC, Hudi and Update-Heavy WorkloadsWhy warehouses struggle when most writes are updates, and how Debezium, Kafka, Hudi and Spark replaced 480 hourly connectors for 200 billion rows.
Read the full analysisOther questions this article answers
More system design & architecture questions
- How much spare capacity should a gateway keep?
- Why are bounded queues important for availability?
- Should a load balancer always move requests away from an unhealthy server?
- Can a circuit breaker prevent every cascading failure?
- Why does pagination improve API performance beyond just 'smaller responses'?
- Why is asynchronous logging faster than writing logs synchronously?
- When does caching actually help API performance, and when doesn't it?
- Why does payload compression trade CPU time for network time, and when is that worth it?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.