FastPubSub Network
Resilient realtime pub/sub over the global Internet
Resilient realtime pub/sub over the global Internet
Your backend publishes one event. FastPubSub delivers it through a mesh that reroutes when paths fail — dashboards and feeds keep updating instead of freezing on a broken route.
Use it when realtime API delivery is part of the product: SaaS notifications, live status, market data, operational dashboards, collaboration events, or customer-facing feeds.
One backend update can need delivery to hundreds, thousands, or millions of connected customers at roughly the same time.
Without a relay fabric, your API tier often ends up holding realtime connections and repeating the same message again and again.
Customers arrive through different ISPs, mobile carriers, and cloud regions. A single direct path is rarely good for everyone.
Your backend sends the event once. FastPubSub handles replication and delivery near subscribed listeners.
The relay mesh measures RTT, jitter, and loss, then shifts traffic away from degraded Internet paths when better routes are available.
Realtime delivery moves out of the origin hot path, so your API servers can focus on product logic instead of connection fan-out.
Status changes, metrics, alerts, and workflow updates pushed to open customer screens.
Small, time-sensitive updates fanned out to many subscribers with lower jitter.
Live notifications, product events, and account updates delivered through WebSocket-compatible pub/sub.
Queues are right for durable work processing. Realtime API fan-out is about delivering the live event while it still changes what the user sees.
CDNs cache objects. FastPubSub moves small live messages through channels to connected subscribers.
Use FastPubSub to fan out API events without turning your origin backend into a global broadcast layer.