Pub/Sub broadcasts only live events to active subscriptions. Independent XREAD readers each replay retained history; one group shares new deliveries. Exact MAXLEN 2 removes the oldest entry. Historical source illustration, not a new service run.

Redis pub/sub and streams are different tools

Redis Pub/Sub and Streams answer different delivery questions. Pub/Sub broadcasts to currently active subscriptions without retaining messages for later replay. A stream stores entries that readers can revisit while they remain retained. Choosing between them starts with who must receive an event and what should happen during a consumer’s absence. ...

February 6, 2028 · 6 min · XB Field Notes
A publication reaches an active subscription while a broken branch marks a subscription gap with no retained replay.

Pub/Sub has no replay: schematic.

Redis Pub/Sub broadcasts without replay

Redis Pub/Sub broadcasts to subscriptions that are active when a message is published. It does not retain an inbox for a disconnected listener. This suits replaceable live notifications, but a positive PUBLISH response is not evidence that a worker finished a job or that an offline consumer can recover it. ...

February 17, 2027 · 6 min · XB Field Notes