backend for frontend
A backend for frontend adapts backend capabilities to a client’s needs.
Use this when A client assembles one screen from many internal service calls.
without the term
“The mobile app makes 8 API calls to different services just to show the home screen. Can we make one endpoint that returns everything the screen needs?”
with the term · How do you ask a model for backend for frontend?
Add a backend-for-frontend endpoint for this screen. Verify the response contract, authorization, and partial dependency failures.
What is backend for frontend?
A backend endpoint built for one client screen collects data from several services and returns exactly what that screen needs. Shared business rules stay in their own services.
Why does backend for frontend matter when vibe coding?
Client-side orchestration can multiply round trips and expose internal contracts.
How do you do backend for frontend?
Define a screen-oriented response and keep shared rules in their authoritative location.
What goes wrong with backend for frontend?
Copying pricing or access rules into a client-specific layer.