Killing BFFs with GraphQL and Next.js
summary
Claims that a Next.js app can replace separate BFFs by hosting a GraphQL endpoint at pages/api/graphql, running an executable schema with express-compatible middleware, calling microservices from resolvers, and deploying serverless. Demo shows a SendGrid example that hides API keys so clients never see sendgrid endpoints. Outcome: one deployable codebase replaces multiple services, removes DNS/deploy overhead, and keeps auth/normalization central — presented as working code.
AI-written summary · about
chapters (8)
- 0:00Introduction to BFFs
- 2:33Monoliths and microservices
- 4:37Benefits of using BFFs
- 7:26Managing service complexity
- 8:37Next.js API routes
- 12:32Practical implementation
- 15:21GraphQL and middleware
- 18:31Course closing and resources
related talks
23mKiling BFFs with GraphQL and Next.js
22mBFF - GraphQL Backend-for-Frontend with React UI
49mBFF (Backend For Frontend)
38mBFF vs GraphQL: A critical perspective
31mReimagining the frontend-backend divide thanks to GraphQL
59mGoodbye REST; Hello GraphQL
37mGraphQL and Microservices or How we learned to be big and small at the same time
21mLive-coding demo