<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scalability on Ehsan Mahmoudi — Blockchain Consultant &amp; Software Architect | Hire Remote</title><link>https://e-mahmoudi.me/tags/scalability/</link><description>Recent content in Scalability on Ehsan Mahmoudi — Blockchain Consultant &amp; Software Architect | Hire Remote</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 16 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://e-mahmoudi.me/tags/scalability/index.xml" rel="self" type="application/rss+xml"/><item><title>How Fanout Broadcasting Powers Millions of Concurrent WebSocket Connections</title><link>https://e-mahmoudi.me/blog/fanout-architecture-millions-concurrent-websockets/</link><pubDate>Sun, 16 Aug 2026 00:00:00 +0000</pubDate><guid>https://e-mahmoudi.me/blog/fanout-architecture-millions-concurrent-websockets/</guid><description>&lt;h1 id="how-fanout-broadcasting-powers-millions-of-concurrent-websocket-connections"&gt;How Fanout Broadcasting Powers Millions of Concurrent WebSocket Connections&lt;/h1&gt;
&lt;p&gt;I&amp;rsquo;ve been working on a chat platform that handles millions of concurrent public chat participants. Early on, I faced the fundamental question every real-time platform asks:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;How do you broadcast a single message to 10,000 people on the same chat simultaneously, across multiple servers, without everything collapsing?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The answer turned out to be simpler than I expected. Not simpler in implementation—the implementation is thoughtful—but simpler in &lt;em&gt;concept&lt;/em&gt;. The pattern is called &lt;strong&gt;fanout broadcasting&lt;/strong&gt;, and I want to walk through it because it&amp;rsquo;s one of those designs where understanding the shape immediately makes you understand why it scales.&lt;/p&gt;</description></item></channel></rss>