Enhance and improve user experience with BFF
summary
Builds a simple e‑commerce app that proves the claim: a Backend For Frontend aggregates product offer and checkout APIs and returns exactly the UI needs, improving UX and resilience. Demonstrates mapping sequential mobile calls into server‑side aggregation, caching, and masking sensitive fields (mask credit card in BFF). Gives rollout and fault examples: 2 seconds vs 10 milliseconds for two endpoints, and a 10% rollout to a new image service with fallback to a default image. Warns about GraphQL adding backend complexity.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:37E-commerce app with microservices
- 3:54What is BFF and why it matters
- 5:20Native apps need BFF
- 6:24BFF simplifies data aggregation
- 7:48Security benefits of BFF
- 8:30BFF enables API combination
- 9:16Gradual backend migration with BFF
- 10:20BFF improves resilience
- 11:27Faster time to market
- 12:31BFF optimizes mobile performance
- 13:13Parallel calls for faster load
- 14:39BFF requires collaboration
- 15:23Double Diamond for BFF
- 17:13Proof of concept approach
- 18:36Frontend handling backend tasks
- 19:18GraphQL and BFF benefits
- 20:00Key takeaways and Q&A session
related talks
21mEnhance and improve user experience with BFF
11mFrontend Development With BFF (Backend for Frontend)
39mBFF, our best friend forever for building lots of frontend apps?
27mBackends for frontends with GraphQL
49mBFF (Backend For Frontend)
38mBFF vs GraphQL: A critical perspective
17mBackend for Frontend – The secret of a great mobile project
54mGiving the Frontend Only What It Needs, or Why You Need a BFF