Engineering blog

Notes from the realtime trenches

Protocol design, distributed fanout, recovery semantics, and the decisions behind Sockudo.

Operations

Running Realtime Infrastructure Across Nodes

How to reason about adapters, duplicate delivery, recovery windows, and push queues in a Sockudo cluster.

Read article
Architecture

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.

Read article
SDKs

Choosing SDK Surfaces for Product Teams

How Sockudo divides responsibilities between realtime client SDKs, server HTTP SDKs, backend proxies, and push provider flows.

Read article