BFF - Best Friend for Frontend
summary
Company replaces fat mobile clients with a small middleware BFF that trims huge web payloads (8 MB, 17–70 s responses) into short, client-tailored GraphQL endpoints, uses Node.js + Express + TypeScript, adds Redis distributed cache and ETag handling, and combines multiple slow monolith calls into one fast BFF request. First feature ("My Work") moves client logic to BFF and a grouping change takes five minutes. Outcome: migrated >70% endpoints and zero production incidents in 2023.
AI-written summary · about
chapters (9)
- 0:00Introduction and energy warm-up
- 3:13The monolith API nightmare
- 10:35Why mobile needed a BFF
- 14:28Choosing the right tech stack
- 20:03Designing the BFF API
- 23:16Migrating from monolith to BFF
- 26:50Performance optimization strategies
- 31:25What not to do in BFF
- 35:43BFF in production and future
related talks
11mFrontend Development With BFF (Backend for Frontend)
20mUnifying gRPC APIs under One Roof: Mastering gRPC Federation for Efficient BFFs
26mBackend For Frontend: Building APIs w. end user in mind
24m2 Fast 2 Furious: migrating Medium's architecture...
36mGraphQL Federation - The @key to Your Platform API Strategy
30mEric Baer - SeattleJS Conference 2017
48mGraphQL Today and Tomorrow
27mA no nonsense GraphQL and REST comparison