Eric Baer - SeattleJS Conference 2017
summary
REST proves chatty in practice — a simple blog page can need 8 API calls and often returns only 17% useful fields (a roughly 6x payload bloat). Mobile and TCP behavior (slow start, radios) make many small requests costly — the example burns over half a second in network overhead on 4G. GraphQL converts many requests into one, serves exactly the requested shape, publishes a schema for tooling, implements in 24+ languages, and can wrap existing REST or databases.
AI-written summary · about
chapters (8)
- 0:00Introduction and welcome
- 1:02Why new API design matters
- 2:51History of API design
- 8:06REST and its limitations
- 12:29Problems with REST APIs
- 19:29Ideal API design principles
- 24:48Introducing GraphQL
- 29:41Q&A and closing
related talks
27mA no nonsense GraphQL and REST comparison
18mIs GraphQL the end of RESTstyle APIs
30mFrom RPC to GraphQL"APIs from Past to Present"
04mSneak peek into the API world outside REST
26mRest, GraphQL & gRPC
46mFrom REST to GraphQL: A 20-Minute Adventure
43mTUTORIAL: We've "REST"ed long enough -- let's have an API adventure!
33mGraphQL Will Do To REST What JSON Did To XML