<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Md Nasim Reza</title>
    <description>The latest articles on DEV Community by Md Nasim Reza (@nasim1717).</description>
    <link>https://dev.to/nasim1717</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1248878%2F8c1b69ec-dfaf-45ca-9f04-854268245cf1.jpg</url>
      <title>DEV Community: Md Nasim Reza</title>
      <link>https://dev.to/nasim1717</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nasim1717"/>
    <language>en</language>
    <item>
      <title>Why don't you lag videos even if 20-30 people talk together in Google Meet or Zoom?</title>
      <dc:creator>Md Nasim Reza</dc:creator>
      <pubDate>Fri, 26 Dec 2025 15:46:30 +0000</pubDate>
      <link>https://dev.to/nasim1717/why-dont-you-lag-videos-even-if-20-30-people-talk-together-in-google-meet-or-zoom-2jok</link>
      <guid>https://dev.to/nasim1717/why-dont-you-lag-videos-even-if-20-30-people-talk-together-in-google-meet-or-zoom-2jok</guid>
      <description>&lt;p&gt;Let's understand how this is possible 👇.&lt;/p&gt;

&lt;p&gt;1️⃣ Full Mesh Connection: That doesn't work! 🚫&lt;br&gt;
Suppose there are 4 people in the meeting: A, B, C, D.&lt;br&gt;
What happens in Full Mesh?&lt;br&gt;
Everyone sends their videos/audio directly to everyone.&lt;br&gt;
A sends B, C, D; B sends A, C, D... It goes on like this.&lt;br&gt;
The result?&lt;br&gt;
As the user increases, the number of connections increases at an explosive rate (n*(n-1) connection for n people!).&lt;br&gt;
Each device has to encode its own video repeatedly.&lt;br&gt;
The CPU, the RAM, the Internet—everything is under a lot of pressure. The mobile heats up, the battery runs out! 🔥&lt;br&gt;
The lag starts after 4-5 people.&lt;br&gt;
That's why Zoom or Google Meet don't use it. Small 1:1 calls are okay, but group calls are impossible!&lt;/p&gt;

&lt;p&gt;2️SFU (Selective Forwarding Unit): The Real Hero! 🦸‍♂️&lt;br&gt;
There is a central media server working here.&lt;br&gt;
How?&lt;br&gt;
Each user uploads their audio/video to the server only once.&lt;br&gt;
The server smartly decides: who will send the stream to, in what quality (HD or low).&lt;br&gt;
Important: The server doesn't encode/decode the video itself—it just forwards!&lt;br&gt;
What is the benefit?&lt;br&gt;
Each has only one upload stream.&lt;br&gt;
Latency is very low.&lt;br&gt;
100+ participants but stable.&lt;br&gt;
Smooth also runs on mobile or low-end devices.&lt;br&gt;
Zoom and Google Meet basically use this SFU architecture—that's what makes them scalable!&lt;/p&gt;

&lt;p&gt;3️⃣ STUN, TURN, ICE: THE SILENT WARRIOR 🛡️ OF THE NETWORK&lt;br&gt;
Not everyone is on the same network—some are mobile data, some are behind office WiFi, some are behind firewalls!&lt;br&gt;
They deal with this problem:&lt;br&gt;
STUN: Extracts your public IP. If direct connection is possible, this is the end of it.&lt;/p&gt;

&lt;p&gt;TURN: Relays through the server when the direct is blocked (takes a little more resources, but the connection is guaranteed).&lt;/p&gt;

&lt;p&gt;ICE: Checks all possible paths and chooses the fastest and most stable route.&lt;br&gt;
Everything is automatic—the user doesn't understand anything!&lt;/p&gt;

&lt;p&gt;4️⃣ Not TCP, UDP: Perfect 🚀 for Real-Time&lt;br&gt;
TCP is very reliable—retransmits when packets are lost. But on a video call?&lt;br&gt;
If you lose a packet, the video freezes, freezes.&lt;br&gt;
UDP is different:&lt;br&gt;
If the packet is lost, the flow continues without waiting.&lt;br&gt;
Maintains real-time smoothness.&lt;br&gt;
Video calls need perfect timing, not perfect data!&lt;/p&gt;

&lt;p&gt;This is why WebRTC (which is used in Zoom and Meet) runs on UDP.&lt;br&gt;
These techs together make our meetings so easy and smooth! 🤩&lt;/p&gt;

</description>
      <category>programming</category>
      <category>networking</category>
      <category>webrtc</category>
    </item>
  </channel>
</rss>
