I'm the original poster. So Microfrontends are basically splitting up a frontend into individually deployable parts much like microservices. We've decided to do

I'm the original poster. So Microfrontends are basically splitting up a frontend into individually deployable parts much like microservices. We've decided to do this because of the number and size of our teams working on our frontend. For a little more on microfrontend this is a good description on the idea: https://micro-frontends.org/ https://micro-frontends.org/ As for the debate, we have a monorepo/microfrontend now and it is quite a bit of work to maintain it and certain parts of it are starting to show the lack of resources put into it. We can't deploy easily individually, our tests are very slow, and crucially our organization thinks there is significant risk in a deployment so they have set a very complicated and long QA process for us to get deployments to production. Realistically I think it is an organizational issue and I've been leaning towards multirepo due to the restricted resources and it would be easier to put some of this work on the teams making the individual parts themselves.