Good article, thanks ! Question though: I´m a fan of multirepos. I normally place frontend in one repo, and each micro service (API) in separate repos. Makes the CI/CD easier and the structure nicer. But this looks like one big pile of code, is it possible to separate frontend/api ?
Software consultant. Bestselling Author. Loves rum, alt culture, games & metal.
Formerly Head of engineering, chief technical architect, head principal engineer, lead dev, etc.
Location
London, UK
Work
Independent Software Consultant at Electric Head Software
This kind of API would more be for your "backend for frontend" - I'd suggest that you put any actual microservices in Azure Web Apps, or Azure Functions apps, and called them by Url as usual.
Thanks, and agree, seems like a good solution. Even though I cant vision what I would put in the "BFF". Sounds more like som helper/utility-stuff. Hmmm.
Software consultant. Bestselling Author. Loves rum, alt culture, games & metal.
Formerly Head of engineering, chief technical architect, head principal engineer, lead dev, etc.
Location
London, UK
Work
Independent Software Consultant at Electric Head Software
Good article, thanks ! Question though: I´m a fan of multirepos. I normally place frontend in one repo, and each micro service (API) in separate repos. Makes the CI/CD easier and the structure nicer. But this looks like one big pile of code, is it possible to separate frontend/api ?
This kind of API would more be for your "backend for frontend" - I'd suggest that you put any actual microservices in Azure Web Apps, or Azure Functions apps, and called them by Url as usual.
Thanks, and agree, seems like a good solution. Even though I cant vision what I would put in the "BFF". Sounds more like som helper/utility-stuff. Hmmm.
Think of a BFF as the "backend logic" of a traditional web application :)