3 ms·
I also see the opposite where a company has a web app product and a public API. The API is also a product. Some front-end developers think the API is the webapp
by karmakaze 3y ago
I also see the opposite where a company has a web app product and a public API. The API is also a product. Some front-end developers think the API is the webapp's API and they shouldn't have to make any tradeoffs.
My suggestion in these cases, is to give the front-end devs a node/express server where they can compose the API calls the way they like and consume that from the webapp. But... they have to own it.
- nerdix 3y agoThis is also known as BFF (Backend For Frontend). Every client gets it's own API tailored for it's use case that will mostly just aggregate/orchestrate calls to the general purpose API. https://samnewman.io/patterns/architectural/bff/ https://samnewman.io/patterns/architectural/bff/
- DanielHB 3y agoSome companies take this even further with a BFF for web, another for Android and another for iOS
- cqqxo4zV46cp 3y agoI’d still put that in the same bucket really. It’s implicitly “a back end for a front end”