gRPC vs REST: let the battle begin!
summary
Clear comparison by building a news-aggregator + voting pipeline with a gateway that can route to either REST (Jersey) or gRPC implementations, plus Zipkin tracing, circuit breakers and simulated failures. gRPC uses HTTP/2 + Netty, protobuf codegen, non‑blocking server-side streaming and enforces distributed deadlines; benchmarks show 2 million req/sec on beefy hardware. Injecting a 750 ms delay into leaderboard services (750 ms injected latency) reveals gRPC’s deadline propagation avoids cascading timeouts while the REST path relies on thread pools and circuit breakers.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 2:16What is REST
- 4:02What is gRPC
- 6:52Microservice problems
- 9:43News aggregator example
- 13:57REST: service discovery and Swagger
- 15:03gRPC: formal service description
- 17:06Async and reactive in gRPC
- 20:37gRPC streaming
- 21:19Content service example
- 23:47Running gRPC server and client
- 25:11gRPC service discovery
- 26:39gRPC performance
- 28:03REST vs gRPC niches
- 29:54Voting demo
- 32:06Cascading failure protection
- 34:55Deadlines in gRPC
- 35:58Tracing and monitoring
- 37:23Mobile app demo
- 40:17Resilience testing
- 41:43REST vs gRPC behavior
- 43:29Conclusions and recommendations
- 44:33Q&A
related talks
46mgRPC vs REST: let the battle begin!
46mREST API vs gRPC, which one should you use in breaking a monolith
01h 15mREST, GraphQL, and gRPC: A Comparison
46mIntroduction to gRPC
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
17mBoost API Performance: gRPC vs REST vs Async
42mREST API vs gRPC, Which One Should You Use in Breaking a Monolith
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma