Giving the Frontend Only What It Needs, or Why You Need a BFF
summary
Maxim Vishnevsky (Mindbox) explains why standard APIs fall short for modern multiplatform systems and argues for using a BFF (Backend-for-Frontend) layer to keep client-specific logic isolated. He also covers scaling challenges that appear when adopting BFF and practical measures to minimize those issues.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:27What is BFF and why it's needed
- 3:12Monolith vs microservices problems
- 7:25When BFF solves the issue
- 13:55How to implement BFF correctly
- 20:23BFF common mistakes
- 25:41BFF architecture and responsibilities
- 30:41Testing and observability of BFF
- 37:05BFF as system problem indicator
- 41:36BFF alternatives and architecture preservation
- 45:07BFF reliability and fault tolerance
- 48:19Selling BFF to the team
- 52:15Gradual BFF transition
related talks
39mBFF, our best friend forever for building lots of frontend apps?
11mFrontend Development With BFF (Backend for Frontend)
40mBFF4EAE: Your Backend's New Best Friend Forever
27mBackends for frontends with GraphQL
21mEnhance and improve user experience with BFF
38mBFF vs GraphQL: A critical perspective
09mKeep your friends close and your APIs closer
17mBackend for Frontend – The secret of a great mobile project