4 ms·
BFF can live on a different stack from the heavier backend, and bear a different development cycle. I've worked in a few orgs where backend devs work on both t
by makeitdouble 4y ago
BFF can live on a different stack from the heavier backend, and bear a different development cycle.
I've worked in a few orgs where backend devs work on both the standard backend and the BFF, often adjusting both when adding new features. It's just convenient to have a separate layer closer to the frontend, dedicated to it.
- warent 4y agoIndeed we see this even comes for free with some stacks like Next.js, in which you can define an api (BFF) to interface with the primary backend. On the surface may sound weird but in practice has actually been pretty great when used mindfully.
- roci89 4y agoWe use Remix in this way. Making calls to multiple endpoints on link prefetch is fantastic for speed
- deleted 4y ago[deleted]
- gherkinnn 4y agoI wish Next.js talked about this some more and beefed up their API routes. Writing your BFF in the same codebase, sharing types, and parsing incoming data on the server without filling up the client bundle is a fab experience.
- antifa 4y agoNuxt3 will have this feature, they call it "nitro" and it uses the npm library called h3 (as opposed to expressjs) under the hood.