Posts tagged BFF
After RFC 10017, the First Reason for a BFF Is Keeping Tokens Out of the Browser
RFC 10017 ranks the BFF first for browser OAuth security because tokens stay on the server. Settle token storage before working on aggregation.
The Framework Server Layer Is Not Your BFF
Keep the framework server layer to browser-facing aggregation; service auth, trust boundaries and risk belong in a standalone BFF, whatever Next or Nuxt can run.
Two Ways to Wire a BFF: htmx Returns Partials, SvelteKit Goes JSON
One call chain, two front ends: htmx partials for admin tables where state lives on the server, JSON over SvelteKit when the client needs to hold state.
A Thin BFF with Fastify
A BFF is a thin translation layer. Fastify v5's schema-driven validation and serialisation hold the boundary, with HMAC signing on downstream calls.
Why BFF Still Earns Its Keep in 2025
A BFF is not a fashionable layer. It is where you make plain who faces the browser, who faces the backend, and who carries the risk.