REST API vs gRPC, Which One Should You Use in Breaking a Monolith
summary
Compares specific tradeoffs for breaking a monolith: REST gives fastest path for CRUD with frameworks like Spring Data and wide language/browser support; gRPC enforces schema-first APIs, auto-generates boilerplate, and uses HTTP/2 and protobuf so messages are smaller and CPU cost is lower. gRPC exposes four RPC patterns (unary, server/client streaming, bidi), has client-side load balancing and synchronous servers, and lacks browser-native consumers. Recommends choosing by consumer type, performance/CPU costs, and whether CRUD or RPC-style calls map better to the problem.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:43REST in Real Life
- 7:29Remote Procedure Call
- 20:07Protocol Buffers
- 24:30Big Difference
- 36:26Some Questions
related talks
46mREST API vs gRPC, which one should you use in breaking a monolith
51mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
46mgRPC vs REST: let the battle begin!
45mgRPC vs REST: let the battle begin!
01h 15mREST, GraphQL, and gRPC: A Comparison
48mChoosing the Right Technology for your API