Discussing Backend-For-Frontend
summary
Claim: Backend-For-Frontend is an organizational pattern to avoid client-specific coordination across microservices; demo builds both a Python Flask BFF and an equivalent Apache APISIX Lua plugin behind a gateway, deployed via Docker Compose to aggregate product/news microservices. The live demo proves aggregation and route rewriting work, and the talk flags the alarming case 60 microservices / 5 developers as evidence that teams—not tech—should drive microservice decisions; advice: don’t split unless you have many developers.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 3:42Overfetching and device constraints
- 5:53Microservices hype and reality
- 12:23Organizational challenges
- 14:56Backend-for-Frontend solution
- 17:05Demo setup with Apache API6
- 20:45Monolith to microservices transition
- 25:11BFF as plugins vs dedicated apps
- 30:36When to use microservices
- 34:30BFF as organizational solution
- 36:15Q&A and resources
related talks
41mDiscussing Backend For Front-end
11mFrontend Development With BFF (Backend for Frontend)
40mScaling Frontend Development
39mScaling Frontend Development
09mKeep your friends close and your APIs closer
39mPatterns for Micro Frontends
21mEnhance and improve user experience with BFF
36mMicrofrontends: Scalability Savior or Unmanageable Maze?