AI Insights

READ OUR LATEST WHITEPAPER: WHAT IS MFE? A COMPLETE GUIDE TO MICRO FRONTENDS

What is MFE?

Since our company has worked with multiple platforms using the MFE approach, we would say that there is a lack of up-to-date and comprehensive information about micro frontends. Martin Fowler provides a fundamental explanation of MFE, and most existing posts are variations of his insights… Building on this foundation, we want to share our own experience with MFE integrations.

What are micro frontends? MFE is inspired by microservices architecture and is useful when a frontend grows too large as a single monolithic SPA. Like microservices, MFE enables more modular and flexible frontend development. Migrating to MFE offers benefits but also introduces challenges that must be addressed properly.

What are not Micro frontends?

Micro frontends are often misinterpreted. Here are common misconceptions:

1. Two separate SPAs using different frontend frameworks without insulation in deployment and data access at runtime

2. A shared component, which is hosted on a side server. It might be a part of MFE, indeed, but only when:

a. It has insolation AND

b. It has been injected dynamically via the orchestrator

3. Small FE application injected into other FE applications without isolation and separation of development by different teams.

Why does this not qualify? Because MFE is not just a design pattern, it is both an architectural pattern and a development approach that impacts both the codebase and the delivery process.

In this detailed whitepaper, we uncover the principles behind Micro Frontends, examine their core concepts and share our own experience with MFE integrations.

View the full whitepaper: What is MFE? A Complete Guide to Micro Frontends, HERE.

Dzmitry Trafimau, Head of JavaScript

Posted 13 Aug 2025

share