Handle Late Data in Streaming

You are designing a streaming pipeline where some events arrive after their event time. Those late records can invalidate previously computed windows, aggregates, or fact tables. The goal is to keep downstream data correct while limiting unnecessary recomputation.

Problem

What this tests

Event-time processing and watermark design
Idempotent writes and deduplication
Repair strategy for very late records
Data quality controls for corrected outputs

Key design signals

Common trade-off·Longer watermark vs lower latencyRecovery pattern·Targeted backfill instead of full replayPrimary challenge·Correctness under out-of-order arrival

Problem

What this tests

Event-time processing and watermark design
Idempotent writes and deduplication
Repair strategy for very late records
Data quality controls for corrected outputs

Key design signals

Common trade-off·Longer watermark vs lower latencyRecovery pattern·Targeted backfill instead of full replayPrimary challenge·Correctness under out-of-order arrival

Problem

What this tests

Event-time processing and watermark design
Idempotent writes and deduplication
Repair strategy for very late records
Data quality controls for corrected outputs

Key design signals

Common trade-off·Longer watermark vs lower latencyRecovery pattern·Targeted backfill instead of full replayPrimary challenge·Correctness under out-of-order arrival

Interview Guides

Problem

What this tests

Key design signals

Problem

What this tests

Key design signals

Handle Late Data in Streaming

Problem

What this tests

Key design signals

Problem

What this tests

Key design signals