What it is
Stream processors group events into windows by when they happened (event time), but events arrive late and out of order. A watermark is the processor’s estimate that no earlier event is still coming; an event-time window fires once the watermark passes its end. This simulator lets you edit the event list and shows each event’s window, when the watermark moves, and which windows fire and why.
When to use it
Use it to understand why a Flink or Beam window fires late, fires twice or never fires: bounded out-of-orderness, allowed lateness and side outputs, an idle partition holding back the minimum watermark, session windows that merge, Beam’s early and late panes, and why processing-time windows give different answers on replayed history.
Gotchas & limits
This is a teaching model of the documented rules in Apache Flink 2.3 and the Apache Beam programming guide, checked on 2026-10-22; behaviour differs between versions. The processing time of each event is an input you set, so timings are illustrative. Real jobs also have checkpoints, state backends and parallelism that are not modelled here.