NODEJS & GRAPHQL COOKBOOK. LET’S TALK ABOUT MICRO-SERVICES
summary
Describes a Node.js + GraphQL microservices engineering stack: schema-first development with code generation that also emits DB migrations; Apollo Federation using Redis to store schemas for resilient pod rollouts; and a batching layer that aggregates downstream calls to fix N+1. Also covers replacing Redux with Apollo Client on the frontend to avoid double normalization, a code generator produced after a year of work, performance planning for very high startup load (~10k req/s), and tracing with Jaeger/Prometheus while noting ongoing versioning and federation integration pains.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:16GraphQL production problems
- 6:36GraphQL origin story
- 10:27GraphQL service alternatives
- 13:42Apollo Client development
- 16:30GraphQL code generation
- 20:27Schema-first vs Code-first
- 23:25Schema stitching and merging
- 26:18GraphQL federation
- 30:59Authorization and context
- 33:07Federation deployment
- 35:59N+1 query problem
- 37:28Production prep and load testing
- 39:14Summary & Q&A
related talks
37mGraphQL and Microservices or How we learned to be big and small at the same time
43mGraphQL in the Era of Server Components
26mSponsored Session: From Prototype to Production: Building Custom GraphQL APIs
59mGoodbye REST; Hello GraphQL
55mGraphQL - APIs the New Way
51mWhy GraphQL is Perfect for Microservices
39mArchitecture of scalable and resilient NodeJS apps with GraphQL & event-driven serverless
41mIntroduction to GraphQL