How do you bootstrap a new table into a CDC-fed lake?
Start the change connector first so changes accumulate in the log, take a consistent snapshot of the table from a known timestamp, load it into the lake format, then replay the log from that timestamp. Snapshot plus replay from the same point leaves no gap and no duplicates.
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.