Enhance and improve user experience with BFF
summary
Builds an e‑commerce demo that stitches existing microservices (product, offer, checkout) behind a Backend‑For‑Frontend that aggregates and caches server‑side and returns UI‑shaped domain objects. Claims: security improves by masking sensitive data in BFF not the client, rollouts use percentage traffic shifts, and native apps avoid forced updates. Shows tradeoffs — e.g. basket 2s vs deals 10ms — and warns GraphQL adds backend complexity; proof‑of‑concepts run fast and then get replaced.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:38E-commerce app with microservices
- 3:48Sequential API calls challenges
- 4:30What is BFF pattern
- 5:58BFF for native apps
- 7:21BFF benefits for security
- 9:08BFF as resilient layer
- 11:14BFF improves time to market
- 12:40BFF on mobile networks
- 13:25Parallel calls optimization
- 14:49BFF in front-end teams
- 16:11Agile with BFF
- 17:36PoC for new features
- 18:39Front-end learns backend
- 19:21BFF and GraphQL
- 20:05Key takeaways
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?
38mBFF vs GraphQL: A critical perspective
54mGiving the Frontend Only What It Needs, or Why You Need a BFF
40mBFF4EAE: Your Backend's New Best Friend Forever
37mDiscussing Backend-For-Frontend
29mNew Trends in Front-End Development (and What We Can Learn from them)