Problem Understanding
Restate the problem in your own words.
Design Zoom / Google Meet (Video Conferencing)
Design a Zoom-class video conferencing system: users join meetings via link, audio + video flow bidirectionally at sub-200 ms end-to-end latency, screen-share is a separate stream, recordings are stored durably, and transcripts arrive within seconds of meeting end. The architecture is unlike anything else in system design — WebRTC over UDP / SRTP, SFU media servers that selectively forward streams, TURN / STUN for NAT traversal, and a fleet sized for sustained bandwidth (Gbps per region) rather than QPS. The decisive trade-offs are SFU vs MCU vs P2P, single-region vs per-region SFU with cascade, and server-side vs client-side recording.
- ZoomThe category-defining product; ~300 M daily participants at peak; SFU-based.
- Google MeetBrowser-first WebRTC; deep G-Suite integration.
- Microsoft TeamsWorkspace + chat + video unified; on Microsoft's media stack.
- Webex / JitsiCisco (enterprise) + open-source (Jitsi); same SFU shape.
Your task: read the problem above, then write what the system is, who uses it, the rough scale, and the headline UX expectation — in your own words. Submit for AI review when you're ready.
Click any step in the sidebar to jump around — sections don't have to be done in order. Press ? any time to see all shortcuts.