Kiling BFFs with GraphQL and Next.js
summary
Claims that BFF services can be removed by running a GraphQL layer inside Next.js API routes, demonstrates an actual demo that merges two REST endpoints into one schema using express‑graphql, exposes a GraphiQL playground, and renders results with getServerSideProps. Shows code for resolvers that fetch posts and authors, mentions json2sdl and stepzen as automation options, and reports the combined endpoint works in the demo while warning about nested-query performance and the need for caching and rate limits.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:01What Are Bffs Good for
- 6:58Api Routes
- 9:44Demo
- 11:28Build a Schema
- 12:10Mock Api
- 13:33Graphical Playground
- 14:39Client Integration
- 20:09A Graphql Api
related talks
20mKilling BFFs with GraphQL and Next.js
22mBFF - GraphQL Backend-for-Frontend with React UI
49mBFF (Backend For Frontend)
38mBFF vs GraphQL: A critical perspective
59mGoodbye REST; Hello GraphQL
01h 02mGoodbye REST APIs. Hello GraphQL!
17mThe Power of GraphQL
26mData Fetching Unleashed: Next.js, React Query and their BFF