160
batch vs stream
Batch has a bounded input and a finish. A stream does not finish. Do not use a stream because it sounds alive.
What is batch vs stream?
A batch job reads a finite dataset and exits. A stream processes unbounded events and stays up. Streaming costs an always-on system and late-data rules. Many “real-time” dashboards are a batch every five minutes, and that is the better design.
Why does batch vs stream matter when vibe coding?
Models reach for Kafka when a nightly job would do. Name the latency the user actually needs.
How do you do batch vs stream?
If an hour of delay is fine, batch. If seconds matter and events already exist, stream, with a watermark. Do not build both “to be safe.”
How do you ask a model for batch vs stream?
(Need) can wait (minutes/hours), so build a batch job, not a stream. If it truly cannot wait, use a stream and state the watermark and late-event rule. Do not introduce a broker for a nightly report.
What goes wrong with batch vs stream?
A micro-batch that is a stream and a scheduler, with two places that can double-apply. Pick one owner of the clock.