Netflix System Design
CDN & Open Connect
Control Plane vs Data Plane
This is the single most important mental model for Netflix architecture. Interviewers expect you to state it clearly.
Control Plane β API Path
Data Plane β After Manifest
OCA Selection Algorithm
Steering Service executes this on every playback session creation, returning a ranked OCA list.
Key Terms
Interviewers expect you to define these without hesitation.
A file (HLS: .m3u8 / DASH: .mpd) listing all available video segments and bitrate variants. Client downloads this first, then decides which quality tier to fetch.
A 2β10 second chunk of encoded video. Player downloads these sequentially. Losing one is recoverable; the player buffers ahead.
Player monitors bandwidth and switches between quality tiers automatically. If network slows, player switches to lower bitrate. Seamless to viewer.
Netflix-custom hardware placed inside ISP data centers. Stores popular video content locally to eliminate transit hops between Netflix and ISP.
Manifest URL is HMAC-SHA256 signed with a 6-hour TTL. CDN validates signature before serving. Prevents URL sharing β the token is bound to the session.
Nightly algorithm predicts next-day popular titles (using recommendation signals + release schedule) and proactively fills OCAs during off-peak hours via ISP peering links.
Why Netflix Built Its Own CDN
At 300 Tbps, commercial CDN transit fees would exceed $500M/year. Netflix instead co-locates ~17,000 OCA appliances inside ISP networks, paying only hardware and negotiation costs. The ISP benefits too: local caching reduces their upstream transit. Cache hit rate for top-200 titles: >99%.