Presenter mode

Netflix (Open Connect & control plane)

Full page · Paths

Walkthrough

Playback control vs OCA bytes

Published Open Connect path: authorize/steer in AWS-shaped control services, then fetch bytes from an OCA. Not a claim of Netflix corporate fabric.

Step 1 / 3
Auth / licensePlayer clientPlayback Apps (AWS)SteeringOpen Connect OCAEncoded media

The player contacts Playback Apps for authorization and licensing. Those control-plane services are described as running in AWS — they are not the byte servers.

Walkthrough

Embedded OCA vs PoP peering

Illustrative roles from partner docs: ISP BGP announcements gate embedded OCA service; PoP peering remains for backup/fill. No invented site map.

Step 1 / 3
ISP memberISP edgeEmbedded OCA (AS40027)AS40027PoP OCA (AS2906)AWS control plane

An embedded OCA only serves client IPs whose prefixes the ISP announces to that appliance over BGP. The ISP controls which customers hit the embedded cache.

Walkthrough

Fault injection & dependency isolation

Teaching resilience from Hystrix + ChAP/FIT publications: isolate dependencies and compare experiment cohorts — not an invented microservice map.

Step 1 / 3
Client cohortAPI / playback pathbulkheadDependencyFIT injectSPS / metrics

Remote calls need timeouts, bulkheads, and circuit breakers so one slow dependency cannot exhaust the caller (Hystrix patterns as published).