BFF, our best friend forever for building lots of frontend apps?
summary
Examines using a Backend-for-Frontend (BFF) pattern to build multiple frontend applications. Describes how a BFF sits between clients and APIs to tailor responses per frontend, reduce client complexity, and manage concerns like aggregation, authentication, and versioning using technologies typical in PHP ecosystems.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 4:19Initial architecture issues
- 6:25New BFF architecture
- 10:21BFF and API Gateway
- 14:11Single Point of Failure risk
- 18:43BFF resilience solutions
- 24:18Team impacts and collaboration
- 27:28Pros and cons summary
- 28:52BFF future evolutions
- 32:43Q&A
related talks
54mGiving the Frontend Only What It Needs, or Why You Need a BFF
11mFrontend Development With BFF (Backend for Frontend)
21mEnhance and improve user experience with BFF
40mBFF4EAE: Your Backend's New Best Friend Forever
21mEnhance and improve user experience with BFF
38mBFF vs GraphQL: A critical perspective
37mDiscussing Backend-For-Frontend
09mKeep your friends close and your APIs closer