Real-time

State that propagates in milliseconds: WebSockets, streams and reactive data.

This hub collects the blocks of live data: WebSocket frameworks, managed realtime platforms, sync engines, event streams and the pub/sub infrastructure behind features whose data arrives while the user is looking at it.

Why it matters to an indie builder: realtime is what makes a product feel alive, presence, collaborative editing, live dashboards, chat, notifications, and it is now infrastructure rather than research. The choice is usually between managing the plumbing yourself, sockets, reconnection, fan-out, state reconciliation, or adopting a platform or sync engine whose SDK handles it.

A realistic pattern: presence and cursors over a managed pub/sub, document collaboration on a CRDT-based sync engine, and live metrics over server-sent events, each the boring, proven option for its job rather than one socket layer for everything.

The trade-off: every realtime feature adds state that must survive reconnects and scale by fan-out, which is exactly what the managed options here absorb. Compare the sync-engine blocks when offline support matters alongside liveness.