Why Multi-Tab Browser Apps Quietly DDoS Their Own Backends
When a browser-based application runs across multiple apps on the same page, or simply across many open tabs, real-time connections start to multiply quickly. Each tab tends to open its own connection, each app on the page does the same, and each reconnect cycle compounds the result further. From inside any single tab the duplication remains invisible, yet at the system level the consequences accumulate: more pipes per user than the system actually needs, more pressure on the backend than it was sized for, and a coordination problem that initially presents itself as a transport problem.
This pattern appears across many real systems, particularly those where multi-tab workflows, micro-frontend boundaries, embedded apps, or independently-owned real-time clients on the same page have to coexist longer than anyone planned. The case described below is one such example, and the rest of the article walks through how it was approached.
Why this happens...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
