From RPC to GraphQL"APIs from Past to Present"
summary
Argues that GraphQL cuts chattiness and payloads by letting clients ask for exactly what they need, converts 8 calls to 1 for a blog example, and shows real-world losses like only 17% of data needed yielding a roughly 6x waste. Quantifies mobile cost: dozens of requests become latency and battery problems, cites a case of ~40 API calls for one page. Demonstrates quick adoption with a demo deployed in seven minutes and notes tradeoffs like partial results and CPU-heavy large queries.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:06INFINITE RED
- 11:17REST is chatty...
- 15:20REST returns too much...
- 16:06REST lacks introspection...
related talks
51mGraphQL: advantages, challenges, and how to overcome them
30mWhy GraphQL vs. Why not GraphQL
06mBeyond REST: Exploring Modern API Paradigms
29mFrom REST to GraphQL
27mA no nonsense GraphQL and REST comparison
23mHarnessing the Power of GraphQL
19mGraphQL: Accelerating Digital Transformation Through Modern APIs.
42mFrom REST to distributed GQL