Realtime systems notes for builders and operators.
Practical essays on protocol evolution, clustered fanout, SDK design, recovery semantics, and operational tradeoffs in Sockudo.
Running Realtime Infrastructure Across Nodes
How to reason about adapters, duplicate delivery, recovery windows, and push queues in a Sockudo cluster.
Designing a Realtime Protocol That Can Evolve
Why Sockudo keeps Pusher compatibility stable while adding native Protocol V2 semantics for recovery, history, and richer clients.
Choosing SDK Surfaces for Product Teams
How Sockudo divides responsibilities between realtime client SDKs, server HTTP SDKs, backend proxies, and push provider flows.