Backend for Frontend (BFF) – the pattern that saved my microservices (and my sanity)
E aí, dev que já teve que explicar por que o frontend mobile precisa de dados diferentes do frontend web? Ou pior: já precisou adaptar uma API monolítica para atender três clientes diferentes e acabou com um endpoint que devolve 50 campos, sendo que cada frontend só usa 10? Pois é. O mundo dos microsserviços é lindo até você precisar entregar uma experiência personalizada para cada tipo de…
The article discusses the Backend for Frontend (BFF) architectural pattern, which involves creating a dedicated backend layer for a specific frontend or group of frontends with similar needs. This approach solves the problem of having a single backend that tries to cater to all frontends, resulting in over-fetching or under-fetching of data.
With BFF, each backend is tailored to the needs of a specific client, such as a mobile app, web app, or admin panel. The article provides an example of implementing a BFF using Spring Boot for a mobile frontend that requires product data, reviews, and stock availability.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
