TL;DR — Most streaming pipelines report latency numbers that measure the wrong thing. The gap between event time and processing time is not a minor implementation detail — it is the fundamental reason dashboards look healthy while business logic silently produces stale or wrong results. Understanding watermarks, late data, and window semantics is the only way to build pipelines that are honest about what they know and when they know it.
Every streaming pipeline has a latency number on its dashboard. That number is almost always a lie — not because engineers are careless, but because most pipelines measure the wrong clock. They report how quickly data moves through the system, not how accurately the system reflects the world that generated the data. Those are completely different things, and conflating them is one of the most persistent sources of silent correctness failures in production data infrastructure.
Two Clocks, One Pipeline
Every event in a stream carries two timestamps.…