Backends for frontends with GraphQL
summary
Claims a separate Backend For Frontend (BFF) per client plus a GraphQL layer lets each UI own a tailored API, cutting unnecessary payloads and round trips and speeding feature rollout by the client team. Implementation uses a GraphQL schema with resolvers that stitch downstream microservices and tooling like Apollo, GraphQL Playground and Voyager. It surfaces tradeoffs explicitly—acceptable code duplication tradeoff and keeping business logic in downstream services—and reports improved performance and faster client-side development.
AI-written summary · about
chapters (4)
- 0:00Start
- 25:08THE API SHOULD BE DESIGNED FOR THE NEEDS OF THE CLIENT
- 25:22DIFFERENT CLIENTS NEED DIFFERENT APIS
- 25:32GRAPHQL ALLOWS YOU TO PUT THE CLIENT IN CHARGE
related talks
22mBFF - GraphQL Backend-for-Frontend with React UI
49mBFF (Backend For Frontend)
38mBFF vs GraphQL: A critical perspective
21mEnhance and improve user experience with BFF
54mGiving the Frontend Only What It Needs, or Why You Need a BFF
17mBackend for Frontend – The secret of a great mobile project
09mKeep your friends close and your APIs closer
37mDiscussing Backend-For-Frontend