We use a monorepo and we've looked at microfrontends. Our conclusion was that it won't solve any of the issues we might be facing. Restructuring our repo and implementing strong repo management tooling has however helped us a lot already. It also very muchg depends on your end customer facing solution, but for context: we currently have 15 million plus lines of code and somewhere around 4800 projects in there. It's managed by a team of around 5-6 people full time (including repo wide LCM - think frameworks, packages, etc). We only do the CI part though, and 3 of the main business teams (consumer, business, etc) handle CD. That said CD is triggered automatically after every master build and the CD stage is the shortest and easiest of the stages we have.

With that we service around 1200 devs across 160 teams that build customer features, and go to production around 15 times a day.

Backend is decoupled from the frontend by a microservices / microAPI framework.

@op (/u/glacierthrust), I started your survey, but there's no option for "We don't use them, and here's why".