Architecting infrastructure for live video streaming is fundamentally different from static Video on Demand (VOD) platforms like Netflix.
With VOD, media files are pre-rendered and distributed to edge caches days in advance. In live sports, the video segment literally does not exist until the split-second the play happens. When a goal is scored, millions of concurrent clients query for the exact same segment manifests at the exact same second—creating a massive thundering herd problem.
During TelevisaUnivision’s 2026 World Cup coverage on Google Cloud (104 live matches, 675M views, 100% availability), GCP deployed a 4-layer edge architecture to keep stream latencies low and origins safe.
🎥 Visual Breakdown & Diagrams
Watch the complete architecture walkthrough and protocol breakdown here:
1. Live Video Ingest: SRT vs. RTMP
Broadcast feeds leave stadiums over dual redundant paths using two distinct transport protocols:
- RTMP (Real-Time Messaging Protocol): Runs over TCP. TCP enforces strict in-order packet delivery. On congested cross-border transit links, losing a single packet causes head-of-line blocking, causing latency to stack up.
- SRT (Secure Reliable Transport): Runs over UDP. SRT uses selective repeat ARQ (Automatic Repeat Re-request) inside a fixed time window. If a packet drops over a rough network link, only the missing packet is retransmitted without stalling the entire video stream.
2. 3-Tier Origin Shielding Topology
If millions of media players hit a single Cloud Storage origin bucket for a brand-new goal segment, the origin storage layer instantly melts. Google Cloud Media CDN solves this using a 3-tier caching structure:
- Tier 1 (Origin Shield / Long-Tail Cache): Aggregates cache misses across all regional edge nodes. A million incoming requests at the front end hit the shield and collapse into a single request back to the origin bucket.
- Tier 2 (Regional Edge Caches): Distributed Points of Presence (POPs) near major metropolitan areas serving active, hot video segments.
- Tier 3 (In-ISP Deep Caches): Cache servers deployed directly inside telecom operator networks across Central and South America. The video segment sits just 1 network hop away from the viewer's phone, completely bypassing congested international transit links.
3. Sub-Millisecond Token Authentication at Kickoff
The heaviest API spike doesn't happen during a goal—it happens at kickoff, when millions of fans open the app simultaneously to authenticate.
TelevisaUnivision containerized session validation APIs on Cloud Run, backed by Memorystore for Valkey 9.0 (an in-memory data store). By eliminating disk I/O, user token validation latency dropped below 1 millisecond, clearing auth bottlenecks before video playout began.
Discussion
Have you worked with high-concurrency video pipelines or origin shielding before? What strategies do you use to survive thundering herd traffic? Drop your thoughts in the comments!
Top comments (0)