Real-Time Streaming Systems (WebRTC + Live Data) · Lesson

SFU vs. MCU Architectures

Understand the differences between Selective Forwarding Units (SFU) and Multipoint Control Units (MCU) for multi-party WebRTC calls.

SFU vs. MCU Architectures is a free Real-Time Streaming Systems (WebRTC + Live Data) lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Real-Time Streaming Systems (WebRTC + Live Data) learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Scaling Multi-Party Calls

Imagine a video call with many people. How do all their video and audio streams connect efficiently? Direct peer-to-peer connections, common in 1-on-1 WebRTC, become complex and inefficient for larger groups.

This lesson explores two main server-side architectures for scaling multi-party calls: MCU and SFU.

Introducing the MCU

MCU stands for Multipoint Control Unit. Think of an MCU as a central 'mixer' for all participants' media streams.

In an MCU architecture, every participant sends their individual audio and video stream to a central server.

How MCU Processes Streams

The MCU server receives all individual streams, decodes them, mixes them together into a single composite stream (e.g., a grid layout of videos), and then re-encodes this single stream.

Finally, the MCU sends this *single, mixed stream* back to *all* participants.

MCU: Client Benefits

A big advantage of the MCU model is that each client only needs to send one stream (their own) and receive one stream (the mixed stream from the server).

This significantly reduces the client's bandwidth and processing requirements, making it suitable for users with weaker internet connections or less powerful devices.

MCU: Server Trade-offs

While beneficial for clients, MCUs place a heavy load on the server. The server has to decode, mix, and re-encode many streams in real-time.

Server Intensive: High CPU and memory usage.
Quality Compromise: Re-encoding can introduce latency and reduce individual stream quality.
Limited Customization: Clients receive a fixed layout determined by the server.

Introducing the SFU

SFU stands for Selective Forwarding Unit. Unlike an MCU, an SFU does not mix or re-encode media streams.

An SFU acts as a smart router, forwarding individual streams from one participant to all others who need to receive them.

How SFU Routes Streams

In an SFU setup, each participant sends their stream to the SFU server. The SFU then forwards each participant's stream *individually* to all other participants.

The SFU can selectively choose which streams to forward and at what quality (e.g., sending a lower resolution to clients with poor bandwidth).

SFU: Client-Side Flexibility

With an SFU, each client receives multiple individual streams (one from each other participant). The client then decodes and renders these streams locally.

This allows for greater flexibility in layout and individual stream control on the client side. For example, a client can choose to display only a few main speakers.

Try running this example:

function simulateSFUClient(numberOfParticipants) {
  console.log("--- SFU Client Simulation ---");
  console.log("Receiving individual streams from server:");
  for (let i = 1; i <= numberOfParticipants; i++) {
    console.log(`  - Stream ${i} (from Participant ${i})`);
    // In a real WebRTC app, this would involve
    // creating a <video> element for each stream.
  }
  console.log("Client renders all streams locally.");
  console.log("----------------------------");
}

simulateSFUClient(3); // Simulate a call with 3 other participants

SFU: Balancing Act

SFUs are highly efficient for the server as they don't decode/re-encode, just forward. This makes them more scalable for many participants.

However, clients need more bandwidth (to receive multiple streams) and more processing power (to decode and render them all locally).

Server Efficient: Low CPU/memory per stream.
Client Intensive: Higher bandwidth and CPU for clients.
Flexible: Clients can customize layout and individual stream visibility.

Choosing the Right Architecture

The choice between MCU and SFU depends on your application's specific needs:

MCU: Best for low-bandwidth clients, fixed layouts, and when server cost for processing is acceptable.
SFU: Ideal for high-quality, flexible layouts, and when scaling to many participants is critical, assuming clients have adequate resources.

SFU vs. MCU Quiz

Test your understanding of MCU and SFU architectures.

Recap: MCU vs. SFU

We've explored two key architectures for multi-party WebRTC calls:

MCU (Multipoint Control Unit): Server mixes streams, sends one composite stream to each client. Good for low-resource clients, but server-intensive.
SFU (Selective Forwarding Unit): Server forwards individual streams to clients. Offers better quality and client flexibility, but requires more client bandwidth and processing.

Choosing between them depends on your specific application requirements and user constraints for scalability and quality.

Frequently asked questions

Is the “SFU vs. MCU Architectures” lesson free?

Yes — the full text of “SFU vs. MCU Architectures” is free to read here on the web, and the Real-Time Streaming Systems (WebRTC + Live Data) course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Real-Time Streaming Systems (WebRTC + Live Data) course, upgrade to CoddyKit PRO.

What will I learn in “SFU vs. MCU Architectures”?

Understand the differences between Selective Forwarding Units (SFU) and Multipoint Control Units (MCU) for multi-party WebRTC calls. You practise Real-Time Streaming Systems (WebRTC + Live Data) with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Real-Time Streaming Systems (WebRTC + Live Data)?

No prior experience is required. Real-Time Streaming Systems (WebRTC + Live Data) on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “SFU vs. MCU Architectures” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Real-Time Streaming Systems (WebRTC + Live Data) lesson?

Yes. Every Real-Time Streaming Systems (WebRTC + Live Data) lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Real-Time Streaming Systems (WebRTC + Live Data)