REST API vs gRPC, which one should you use in breaking a monolith
summary
Compares concrete tradeoffs: gRPC is schema-first with generated Java stubs, uses HTTP/2 + protobuf for smaller payloads and lower CPU, and supports four RPC patterns (unary, server stream, client stream, bidi); shows working bank-transfer and notification examples (proto, server and blocking/nonblocking clients, channel setup) and notes gRPC web is new. REST is flexible and often implemented as CRUD REST via Spring with many frameworks and no required schema. Choice hinges on consumer (mobile/backend), performance needs, and existing company policies.
AI-written summary · about
chapters (4)
- 0:00Start
- 39:43What is the use case?
- 40:13What are internal policies and rules?
- 40:56What is the problem
related talks
42mREST API vs gRPC, Which One Should You Use in Breaking a Monolith
46mgRPC vs REST: let the battle begin!
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
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
45mgRPC vs REST: let the battle begin!
17mBoost API Performance: gRPC vs REST vs Async