Re:The Hidden Complexity of Scaling WebSockets
by dboreham on Friday January 24, 2025 @06:37PM
(#42817998)
The trick to doing this efficiently is to arrange for the live session state to be available (through replication or some data bus) at the alternative back end before cut over.
[ Parent
| on HN ]
Re:The Hidden Complexity of Scaling WebSockets
by xyzzy123 on Saturday January 25, 2025 @07:00AM
(#42821137)
When you really think about this though you start to wonder whether incrementalism is worth it, the general case is a resync from the client...
i.e, what are you buying with events streamed to client vs polling and "get me events later than I have". A robust protocol ends up looking like websockets being a way to say "something happened" but refreshes and reconnects are always running the "please catch me up on everything" case.