GraphQL, gRPC or REST? Resolving the API Developer's Dilemma
summary
Compares practical tradeoffs: gRPC uses HTTP/2 + protobuf, gives fast multiplexed RPC and streaming but isn’t browser-native and needs proxies for HTTP/1.x; GraphQL excels as a composite/facade and BFF solution, enables GitHub-style client SDKs and uses persistent queries to enable caching tradeoffs, yet lacks a single HTTP spec and pushes performance tuning to the right; REST embraces hypermedia (HATEOAS) for evolvability and intermediary caching, and HTTP/2 plus server push often removes the need for compound responses.
AI-written summary · about
chapters (15)
- 0:00Start
- 14:06API PARADIGM SHIFTS
- 19:10CONSTRAINTS
- 31:33SO API STYLES...
- 41:15HTTP/2 SERVER PUSH
- 41:58SO PERFORMANCE...
- 45:43GRACEFUL EVOLUTION
- 46:50INTEGRATION PATTERN FROM MARTIN FOWLER
- 48:50CONTRACT FIRST
- 49:36SO VERSIONING...
- 51:19SO API DESIGN...
- 52:12SAMPLE SCENARIOS
- 52:36APPLICATION WEB FORM
- 53:10COMPOSITE API
- 57:19TAKEAWAYS
related talks
01h 15mREST, GraphQL, and gRPC: A Comparison
45mREST, gRPC, SignalR and GraphQL for .NET developers
46mREST API vs gRPC, which one should you use in breaking a monolith
42mREST API vs gRPC, Which One Should You Use in Breaking a Monolith
26mRest, GraphQL & gRPC
48mChoosing the Right Technology for your API
50mREST, gRPC, GraphQL, Webhooks: When to Use Each?
46mgRPC vs REST: let the battle begin!