Backend for frontend (BFF) in front of services
FreeSystem map@rabbinatix/bff-architecture by Rabbinatixupdated Oct 13, 2026
The website talks to one BFF, which gathers what each page needs from the services behind it.
4 systems and 3 APIs. Every API is declared on both sides, so every contract starts healthy. Rename or change anything once it is on your map.
3 connections · 3 APIs
- Web App → Web BFF
GET /bff/v1/dashboardEverything the dashboard page shows
- Web BFF → Users Service
GET /api/v1/users/{id}One user
- Web BFF → Orders Service
GET /api/v1/ordersA user’s orders
Systems (4)
Web App
The website.
Web BFF
Shapes data for the website’s pages.
Users Service
People and their profiles.
Orders Service
Orders and their status.
A system you already have under the same name is used, not copied. Outside APIs don't count towards your plan.
Versions
