TUTORIAL: We've "REST"ed long enough -- let's have an API adventure!
summary
Compares REST, event-driven, GraphQL and gRPC with concrete tradeoffs: REST stays ubiquitous but mostly HTTP/1.1 and suffers overfetching; async patterns use asyncio and a compact websocket echo example in Python to show long-lived connections; gRPC uses proto files over HTTP/2, auto-generates client/server stubs and claims about 7–10x faster RPCs due to binary framing and compression; shows Postman can import specs and generate code, and highlights deployment, tooling and design complexity costs.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:09Understanding REST APIs
- 8:07Limitations of REST and HTTP
- 14:30Event-driven APIs
- 23:47Introduction to gRPC
- 32:19Comparing API architectures
- 38:36Choosing the right API
related talks
17mBoost API Performance: gRPC vs REST vs Async
01h 15mREST, GraphQL, and gRPC: A Comparison
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
46mREST API vs gRPC, which one should you use in breaking a monolith
46mgRPC vs REST: let the battle begin!
50mREST, gRPC, GraphQL, Webhooks: When to Use Each?
01h 01mAn Architect's Approach to API Strategies
46mREST, GraphQL, gRPC, Webhooks: when to use each?