Microfrontends should be a last resort
Personally, I wouldn&#x27;t call it a &quot;last resort&quot;, but I definitely agree that keeping a functioning monolith is preferred.<p>Nevertheless, one thing to keep in mind (and I do consulting on MF for the last 5 years) is that most projects &#x2F; teams are not well prepared and actually not at all suited for MF. MF solutions are usually just done from a technology POV, which is already a problem. Next thing is that the used technologies are often also not well suited. People tend to use strongly coupled things that just create hidden monoliths. In the end projects fail often because either the organization is not ready to have truly independent teams or &#x2F; and because the software has just become too complex and unmaintainable.<p>To end with something positive: We also know many success stories in that area where people spent the right amount of research on what technologies to use and where everyone in the organization was prepared to accept the new teams setup.