Google Meet

Overview

Google Meet is a video conferencing service built on open web standards (WebRTC) and tightly integrated with Google Workspace (Calendar, Gmail, Docs). It supports meetings of up to 1,000 participants with live streaming to 100,000 viewers. Meet’s architecture leverages Google’s global network backbone for low-latency media transport, server-side media processing for adaptive quality, and a progressive web approach that requires no client installation. Its design prioritizes reliability, accessibility, and seamless integration over protocol-level customization.

Scale

Requirements

High-Level Architecture

Loading diagram...

Key Components

Data Model

Loading diagram...

WebRTC and OASIS Media Routing

Meet is built entirely on WebRTC, the open standard for real-time communication in browsers. This means no plugin or desktop app is required — any modern browser can join a meeting.

OASIS is Google’s custom media relay infrastructure, deployed at 200+ edge Points of Presence (PoPs) globally. When a participant sends video, it travels to the nearest PoP, then traverses Google’s private backbone (not the public internet) to reach other participants’ nearest PoPs.

Simulcast: Each client sends multiple quality layers of their video (e.g., 720p, 360p, 180p). The OASIS router selects which layer to forward to each recipient based on their available bandwidth and display size. This avoids server-side transcoding for most cases.

Bandwidth estimation: OASIS performs server-side bandwidth estimation for each participant using REMB/transport-cc feedback. When a participant’s network degrades, the router instantly switches to a lower simulcast layer — the sender doesn’t need to change anything.

Loading diagram...

Server-side Noise Cancellation

Meet performs server-side noise cancellation using a deep learning model, a differentiator from most competitors that rely on client-side processing.

Why server-side?: Running the ML model server-side means it works on every device — including low-powered Chromebooks and phones — without draining the battery. It also ensures consistent quality regardless of client hardware.

Model architecture: A lightweight RNN-based model processes audio frames in real time with <10ms additional latency. It separates human speech from background noise (typing, construction, pets, etc.).

Deployment: The model runs on Google’s TPU infrastructure at the media processing layer. Each audio stream is processed independently before being forwarded to other participants.

Google Workspace Integration

Meet’s deep integration with Google Workspace is a core architectural decision that shapes its design.

Calendar-native: Meetings are created as Calendar events. The meeting ID and join link are embedded in the event, and Calendar handles invitations, reminders, and RSVP tracking. There’s no separate meeting management system.

Gmail integration: Meet links appear in Gmail, and users can join meetings directly from email threads. Meeting notes are auto-linked to Calendar events and stored in Google Docs.

Drive integration: Recordings and transcripts are automatically saved to the organizer’s Google Drive with appropriate sharing permissions inherited from the Calendar event.

Authentication: Meet uses Google’s centralized identity system. Workspace admins control meeting policies (who can join, recording permissions, etc.) via the Admin Console, which propagates to Meet through Google’s policy engine.

Architectural Tradeoffs

# Learn From a Google Meet-like System

You are an expert software architect and teacher. I want to learn from a Google Meet-inspired system design (WebRTC-powered video conferencing deeply integrated with Google Workspace) without pretending this is the exact private production architecture.

Use the following reference as a learning model. Keep assumptions visible, avoid unsupported scale claims, and explain the engineering forces behind each design choice.

---

## System Design Reference
import { Mermaid, Scale, ComponentList, ComponentCard, Requirements, Tradeoff } from '@/components/mdx';

## Overview

Google Meet is a video conferencing service built on open web standards (WebRTC) and tightly integrated with Google Workspace (Calendar, Gmail, Docs). It supports meetings of up to 1,000 participants with live streaming to 100,000 viewers. Meet's architecture leverages Google's global network backbone for low-latency media transport, server-side media processing for adaptive quality, and a progressive web approach that requires no client installation. Its design prioritizes reliability, accessibility, and seamless integration over protocol-level customization.

## Scale

<Scale items={{
  "Daily meeting participants": "300M+",
  "Max participants per meeting": "1,000",
  "Live stream viewers": "100,000",
  "Global PoPs": "200+",
}} />

## Requirements

<Requirements
  functional={[
    'Video and audio conferencing with screen sharing',
    'Calendar integration with one-click join',
    'Live captions and meeting transcription',
    'Breakout rooms and polls',
    'Recording to Google Drive',
    'Live streaming to large audiences',
    'Background blur and virtual backgrounds',
  ]}
  nonFunctional={[
    'Low latency media delivery (\<150ms glass-to-glass)',
    'Adaptive quality based on network conditions',
    'Browser-native — no plugin or app required',
    'End-to-end encryption for small meetings',
    'Global availability via Google edge network',
   ...

[Full prompt copied to clipboard]