Why does a runtime that cuts an endless input into repeated small finite jobs need no marker flowing with the records?

## The seam **Repeated small finite jobs** means serving an endless input by cutting it into short bounded pieces and running a complete little job over each one. At the end of each little job there is a real boundary — a seam — at which every unit of work for that piece has finished, any redistribution inside it has completed, and nothing has started for the next piece. No record is travelling between workers, and no worker is halfway through an update. That is precisely the property a coherent picture needs. Consistency means every saved part corresponds to the same prefix of the input, and at the seam the parts already do, with nothing having to travel through the dataflow to make it so. The runtime writes, to **durable shared storage for recovery points** — storage outside any one machine, reachable from whichever machine picks the work up: - the values the workers have accumulated over the pieces completed so far; - the **recorded read position** covering exactly those pieces and no more. By contrast, **record-at-a-time processing** — where each record moves through the whole job as it arrives and workers hold values between records — never has such a moment. It manufactures one with a marker travelling with the records: a special element injected into the stream that each worker passes along after saving its own part. ## What the seam costs The boundary is not free, and the way it is not free shapes the whole design: - **A latency floor.** A record cannot influence output before the piece containing it completes, so end-to-end delay cannot fall below the piece length plus the little job's own overhead. - **Fixed overhead, multiplied.** Each little job costs a scheduling round and some coordination whatever its size, so halving the piece length does not halve latency in practice; below some length, overhead is most of the work. - **A coupled cadence.** The capture interval is tied to the piece cadence rather than chosen independently, so 'process in very short pieces but capture rarely' is not free unless the runtime separates the two. - **Long pieces cost twice.** A longer piece raises latency and also raises how much input a crash makes you reprocess, because the picture only advances at seams. ## The three shapes side by side | Runtime shape | Where the coherent picture comes from | What it pays | |---|---|---| | Repeated small finite jobs | The seam between pieces | Latency floor, per-piece overhead, coupled cadence | | Record-at-a-time | A marker travelling with the records | Reconciling several inputs at fan-in, and an interval to choose | | Two-phase disk-to-disk | Nothing is captured from a running job: each phase is materialised to durable files | Writing and re-reading every phase from disk | ## Why neither is simply better The seam buys a simpler recovery story — no cut moving through the records, nothing to reconcile where two inputs meet, and a boundary that is easy to reason about — and pays in latency. The marker buys lower latency and pays in reconciliation and in an interval that has to be tuned. Which a job needs follows from the delay its consumers tolerate, not from which mechanism sounds more sophisticated. Some runtimes now offer both shapes behind one programming surface, so it is not even always a choice of product. ## What the seam does not change It makes the picture *easy to take*; it does not make it *cheap to write*. The bytes are still the accumulated values, they still travel to storage outside any one machine, and every worker still writes at roughly the same time. Nor does it change what a destination sees: records reprocessed after resuming from the last completed seam produce their output a second time, and only an arrangement at the destination makes that repeat invisible. ## What an interviewer is checking Mostly one thing: whether you state a mechanism as *the* mechanism. A candidate who says continuous processing recovers by injecting markers into the stream has described part of the market and asserted it as the class. The answer that lands names the quiet moment as the alternative, says what that quiet moment costs, and treats the choice between them as a latency decision.