← Graph

REST

concept 3 connections

Dominant architectural style for HTTP APIs. Critiqued in the talk for forcing clients into N+1 fetches (video, channel, each comment, each author, next video, next channel, …) and, in YouTube's case, for leaking server-side internals — the 'part' parameter, snippets vs contentDetails, and per-part quota costs — into every client. Motivates GraphQL, Falcor, and Pathom/EQL.

category
architecture
about
REST concept
Talk critiques REST and YouTube's 'part' quota system.
Talk frames alternatives in contrast to REST as the default.
about
REST concept
Shared dictionaries can compress REST JSON payloads.

Provenance

Read by
2 extractions