Rest, GraphQL & gRPC
summary
Microservices drive a Back‑end‑for‑Front‑end layer that is implemented here with REST, GraphQL and gRPC, with concrete demos: a minimal GraphQL server and a gRPC server, proto files compiled to proto‑generated TypeScript interfaces, Apollo cache control for field TTLs, and an NPM pipeline idea for publishing protobufs. Measured latency for 1,000 simple requests is ~2.1–2.3s for GraphQL versus ~270ms for gRPC, showing the performance tradeoffs alongside debugging and tooling limits.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:38Microservices
- 2:03monolith
- 2:20micro services
- 2:41advantages
- 4:58BFFs
- 6:25Mobile
- 7:04GraphQL
- 7:16Rest vs GraphQL
- 9:33GraphQL cache control decorator
- 11:26What is gRPC
- 11:43Remote Procedure Call
- 11:56gRPC
- 12:11gRPC features
- 12:52gRPC contract
- 21:23gRPC disadvantages
- 22:43gRPC setup
- 23:16Interview
related talks
01h 15mREST, GraphQL, and gRPC: A Comparison
51mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
43mGraphQL in the Era of Server Components
46mgRPC vs REST: let the battle begin!
45mREST, gRPC, SignalR and GraphQL for .NET developers
37mGraphQL and Microservices or How we learned to be big and small at the same time
27mA no nonsense GraphQL and REST comparison