Three stores, two cursors: where an SSE consumer should resume

Tue, 15 Sep 2026 00:30:00 +0530

Picture a service consuming events over Server-Sent Events: a handful of long-lived streams, one owning pod each, running all day. For a consumer like this the interesting code isn’t the parsing. It’s what happens when the stream breaks, because it will, and the only question that matters then is where do you start reading again.

Every SSE guide answers that the same way: Last-Event-ID. Keep the id of the last event you saw, send it on reconnect, the server resumes after it. That’s the protocol’s answer and it’s a good one.

Kotlin on Tushar Choudhary

Three stores, two cursors: where an SSE consumer should resume