Case study boundary
Use this as a learning model.
This page explains architectural patterns and constraints inspired by Zoom. It should not be read as the exact private production architecture or as a one-size-fits-all recommendation.
Evidence
Public info + inference
Learn first
Concepts behind this architecture
WebSocket
Keep a bidirectional connection open for low-latency client and server messages.
CDN
Cache and serve content close to users so origin systems stay fast and protected.
CRDT
Let distributed replicas accept local edits and merge without conflicts.
Operational Transform
Transform concurrent edits so collaborative documents preserve user intent.
Overview
Zoom is the world’s most widely used video conferencing platform, serving 300M+ daily meeting participants. Unlike browser-based competitors, Zoom uses a native desktop client with proprietary media codecs and a globally distributed Multimedia Router (MMR) infrastructure. Its architecture is purpose-built for video quality, supporting up to 1,000 video participants and 49 simultaneous on-screen feeds. Zoom differentiates through its hybrid cloud architecture (supporting on-premise deployments for enterprises), breakout rooms, and a telephony-grade reliability SLA.
Scale
300M+
Daily meeting participants
~25M
Peak concurrent meetings
1,000
Max video participants
18+ worldwide
Data centers
Requirements
Functional
- HD video conferencing with gallery and speaker views
- Screen sharing with annotation
- Breakout rooms with automatic/manual assignment
- Virtual backgrounds and touch-up appearance
- Waiting room and host controls
- Meeting recording (local and cloud)
- Zoom Phone (PSTN integration) and Zoom Rooms
Non-Functional
- Low latency (<150ms glass-to-glass)
- High video quality up to 1080p
- Reliability — 99.999% uptime SLA
- On-premise deployment option for regulated industries
- Bandwidth efficiency on constrained networks
- Support for 1,000+ participants per meeting
High-Level Architecture
Key Components
Multimedia Router (MMR)
Zoom’s core media handling component — a custom SFU that receives, processes, and selectively forwards audio/video streams. MMRs are deployed in 18+ data centers and handle codec negotiation, simulcast layer selection, and bandwidth adaptation. Each meeting is assigned to an MMR based on participant geography.
Signaling Server
Manages meeting lifecycle — creation, join, leave, host controls, breakout rooms, and waiting rooms. Communicates with clients over HTTPS/WebSocket and coordinates participant state across MMRs.
Zoom PoP Edge
Points of Presence at 50+ locations worldwide that provide the nearest entry point for client connections. PoPs minimize the public internet hops for media traffic by routing it onto Zoom’s private backbone as early as possible.
Recording Service
Captures meeting media server-side for cloud recordings or processes local recordings on the client. Cloud recordings are transcoded into multiple formats and stored with automatic transcription.
PSTN Gateway
Bridges traditional telephone calls into Zoom meetings. Handles SIP/H.323 interop for Zoom Rooms and dial-in participants. Integrates with Zoom Phone for PBX functionality.
Breakout Room Manager
Dynamically creates sub-meetings within a parent meeting. Each breakout room gets its own MMR session while maintaining the ability to broadcast messages from the host and recall participants to the main room.
Data Model
Multimedia Router (MMR) Architecture
The Multimedia Router is Zoom’s secret weapon — a highly optimized SFU written in C/C++ for maximum performance.
How it works: Each meeting is assigned to an MMR. Participants send their encoded video to the MMR, which decides what to forward to each recipient based on:
- Active speaker detection: The current speaker’s video is prioritized
- Gallery view layout: Up to 49 video tiles, each receiving an appropriate resolution
- Bandwidth estimation: Each participant gets the highest quality their connection can handle
Multi-MMR meetings: For geographically distributed meetings, Zoom cascades multiple MMRs. A meeting with participants in the US and Europe might use MMRs in both regions, with the MMRs exchanging media over Zoom’s backbone. This keeps latency low for all participants.
Proprietary codecs: While Zoom supports standard codecs (H.264, VP8), it also uses proprietary codecs optimized for screen sharing (high resolution, low frame rate, text-optimized) and low-bandwidth scenarios.
Hybrid Cloud and On-Premise Architecture
Zoom offers a unique hybrid cloud deployment model that many competitors lack.
Meeting Connector: Enterprises can deploy Zoom MMRs on-premise. Media stays within the corporate network while signaling still goes through Zoom’s cloud. This satisfies data sovereignty requirements for government and financial customers.
Zone-based routing: Zoom’s infrastructure uses zones to control where media is processed. An admin can mandate that meetings for their organization only use MMRs in specific geographic zones (e.g., “EU only” or “on-premise only”).
Failover: If an on-premise MMR fails, the meeting automatically migrates to Zoom’s cloud infrastructure. Participants experience a brief reconnection but no meeting termination.
Zoom Phone: Extends the hybrid model to telephony. On-premise SBCs (Session Border Controllers) connect to the PSTN while call control runs in Zoom’s cloud.
Breakout Rooms at Scale
Zoom’s breakout rooms are architecturally interesting because they create sub-meetings within a meeting.
Implementation: Each breakout room is a separate MMR session with its own media routing. The parent meeting’s signaling server maintains the mapping of participants to rooms.
Host broadcast: When the host broadcasts a message to all rooms, the signaling server sends it to each breakout room’s session. For audio broadcasts, the host’s audio stream is temporarily mixed into each room’s MMR.
Participant movement: Moving participants between rooms requires tearing down their media session in one room and establishing it in another. Zoom optimizes this by pre-allocating MMR capacity for the expected number of rooms.
Scale: Zoom supports up to 50 breakout rooms per meeting, each with its own participant limit. The parent meeting can have 1,000 participants distributed across rooms, with the host maintaining visibility into all rooms simultaneously.
Architectural Tradeoffs
Native desktop client over browser-first
Pros
- +Full control over codec and rendering pipeline
- +Better performance and lower latency
- +Access to OS-level features (virtual audio, screen capture)
Cons
- −Requires installation — friction for first-time users
- −Must maintain clients for every OS
- −Browser client is a second-class experience
Proprietary codecs alongside standards
Pros
- +Optimized for specific use cases (screen sharing, low bandwidth)
- +Competitive advantage in quality
- +Can evolve independently of standards bodies
Cons
- −Not interoperable with standard WebRTC clients
- −Higher engineering cost to maintain
- −Lock-in risk for customers
Hybrid cloud / on-premise option
Pros
- +Wins regulated enterprise customers
- +Data sovereignty compliance
- +Media stays on corporate network
Cons
- −Significant engineering complexity
- −On-prem hardware maintenance burden for customers
- −Feature parity lag between cloud and on-prem
Learn From Zoom
Copy a learning context prompt for an AI assistant. It keeps assumptions visible and asks for tradeoffs, cost drivers, failure modes, and what to measure before adding complexity.