Presenter mode

API gateway & edge termination

Full page · Paths

Walkthrough

Client → gateway → service

Illustrative north–south request: TLS/auth/throttle at the gateway, then a backend hop. Product-pattern pedagogy — not a company-private topology.

Step 1 / 3
HTTPS requestClientAPI gatewayBackend serviceStore

The client opens a north–south call. The API gateway is the first hop that can terminate TLS and apply shared policy before any backend sees the request.

Walkthrough

Netflix: API control vs Open Connect bytes

As published: Playback Apps authorize/license; Steering returns ranked OCA URLs; bytes come from Open Connect — not from the API hosts. Control plane ≠ byte plane.

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

Player talks to Playback Apps (AWS control plane as published). Auth and licensing happen here before any media URL is trusted.

Walkthrough

Edge sheds overloaded clients

Illustrative throttle: gateway rejects excess requests while the backend still has capacity. Product docs expose throttling knobs — not company quota values.

Step 1 / 3
Burst trafficClientAPI gatewaytoken bucket (illustrative)Backend serviceStore

Clients send a burst. Gateways and proxies publish configurable throttling; treat numbers on this page as teaching inputs, not Netflix/AWS production quotas.