Boost API Performance: gRPC vs REST vs Async
summary
Compares measurable tradeoffs: REST causes overfetching/underfetching and sticks to HTTP/1.1 patterns while GraphQL fixes payload selection; async options use WebSockets, WebHooks, server‑sent events for event streams; gRPC runs on HTTP/2 with protocol buffers, supports four streaming modes (unary, client, server, bidi), needs browser proxies and is mostly internal today, and claims about latency show gRPC is typically 7–10x faster than typical REST JSON APIs.
AI-written summary · about
chapters (10)
- 0:00API performance intro
- 1:07REST meaning and limits
- 3:13HTTP 1.1 flaws
- 5:46Event-driven APIs
- 8:54Optimizing API performance
- 9:59gRPC vs REST with HTTP/2
- 12:30REST vs gRPC vs async
- 13:53Balancing API choice with team and infrastructure
- 14:58HTTP/3 future
- 16:03Summary and Q&A
related talks
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
43mTUTORIAL: We've "REST"ed long enough -- let's have an API adventure!
01h 15mREST, GraphQL, and gRPC: A Comparison
46mREST API vs gRPC, which one should you use in breaking a monolith
43mComparing API Protocols - One Feature at a Time
46mgRPC vs REST: let the battle begin!
28mFrom Backend Powerhouses to Web-Friendly APIs: Unlocking
50mREST, gRPC, GraphQL, Webhooks: When to Use Each?