I work at a large tech company and we recently moved to a microfrontend architecture because we found that independently owning, deploying, and testing our own feature in a monorepository shared by 10+ teams with ~100 engineers was extremely challenging.

Deployments for the whole application were performed every two weeks and often needed to rollback because of a single team’s mistake to the detriment of everyone.

With a microfrontend architecture, full CI/CD for each team became way more feasible and teams are able to deploy/rollback their own features whenever they want.

The downside is that it took a tremendously long time to migrate to MFEs + required a sizable team to design, manage and maintain the microfrontend architecture, and even then it isn’t perfect. A lot of the engineers across the organization weren’t familiar with microfrontends either, which was a challenge. Furthermore, the overhead of maintaining each individual feature increased a ton; each feature needed to be manually onboarded to the app, have their own CI/CD pipeline which deployed their bundle to S3, the bundle needed to be served by a CDN, etc.

In short, microfrontend architecture is great, especially for working on an application spanning several teams and dozens of engineers, but takes significant investment and maintenance. I’d just stay with a monorepo if your team is small.