Fan-Out

What Is Fan-Out?

Fan-out is a message pattern where one event is sent to many destinations. In a chat or community product, this could mean one message going to every user in a channel, every member of a group, or all connected clients that need the update.

It is a simple concept, but it becomes difficult at scale. A message may need to reach ten users, ten thousand users, or even a larger live audience. The system has to determine who should receive it, where those users are connected, and how quickly the message needs to be delivered.

You usually meet fan-out in publish/subscribe systems, notification systems, activity feeds, comment threads, live chat applications, and event-driven architectures.

Fan-Out in Real-Time Chat

Fan-out takes a message sent in real-time chat and turns it into many delivered messages.
When a user makes a post in a group chat, livestream chat, or community channel, the backend needs to route this message to the right connected clients. This might include active WebSocket connections, permissions, muted users, online status, device state, and offline delivery. 
To the user, it seems simple - they post a message, and others see that same message show up. Fan-out is doing the distribution work underneath. 

Fan-Out on Write or Fan-Out on Read 

Fan-out is usually handled in one of two ways.

Fan-out on write means the system sends or prepares the message for receivers when the message is created. This can make reading faster later, but writing becomes heavier when the message has many recipients.
Fan-out on read means the system waits until a user opens a chat, feed, or view, and only then retrieves the relevant messages. This can make writing lighter, but reading may take more work.
There is no single better option here. The choice depends on audience size, latency requirements, storage design, and whether users often come back to read the content later.

How Fan-Out Works for Digital Products

Fan-out is important because many digital products rely on shared real-time activity. A chat message, a reaction, poll results, or a badge update may need to reach several users at once. 
Fan-out is a scaling problem in live streaming, gaming environments, or sports platforms with active communities. The system needs to send updates fast without overloading servers, duplicating work unnecessarily, or disrupting the conversation. 

It also connects with moderation. Some products place spam checks, permissions, rate limits, or moderation rules before fan-out, so one bad message does not immediately reach a wider audience.

The basic idea stays the same: fan-out is not just about sending something to many people. It is about making sure the delivery is fast, safe, and handled in the right context.