Go Realtime Channels Should Notify, Not Store, Logistics Device State
A realtime channel should deliver current logistics device events to authorized dashboard clients, but it should not serve as the record of those events. Durable device state belongs in a database or log, with a small notification published afterward so clients know what changed. On reconnect, clients should read from the durable source before resuming the live stream, since a reconnected socket does not prove missed updates were received. Connection tokens should be scoped to tenant, facility, and topic, because browser clients are untrusted even when their users are. The author also recommends separate service targets for durable ingestion and dashboard freshness, and testing the gap between them.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in