GraphQL, REST or RPC? Making the choice!
summary
Clear claims and tradeoffs: JSON‑RPC and gRPC make RPC feel like calling remote functions and explain why Ethereum picks JSON‑RPC; REST leverages HTTP/2, status codes, e‑tags and content negotiation so caches and raw image responses work; GraphQL lets clients pick fields and reduce round trips but can DDoS servers without complexity limits and needs Relay/global ID patterns for sensible pagination. Concrete examples include a GraphQL author/books query (returns a totalCount of six in the demo) and an RPC POST-based method call that returns a result.
AI-written summary · about
chapters (8)
- 0:00Introduction to API styles
- 2:38Understanding RPC APIs
- 8:20Deep dive into RESTful APIs
- 17:40GraphQL architecture and use
- 25:13Selecting the right architecture
- 35:28Versioning and API evolution
- 40:47Design challenges and patterns
- 52:10Errors, docs, and conclusions
related talks
51mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
27mA no nonsense GraphQL and REST comparison
42mREST API vs gRPC, Which One Should You Use in Breaking a Monolith
46mREST, GraphQL, gRPC, Webhooks: when to use each?
30mFrom RPC to GraphQL"APIs from Past to Present"
26mCreate API for your databases, Rest, GraphQL, gRPC which one should you choose ?
33mGraphQL Will Do To REST What JSON Did To XML
