Extending Module Federation to a true Micro-apps Pattern
Imagine you are part of a team that manages a very large e-Commerce app (think of Amazon.com). For such large sites, it is a common practice to have teams that own a single organism-level component (https://atomicdesign.bradfrost.com/chapter-2/#organisms) instead of the entire mini app.
For example, we have a dedicated team that works exclusively on the Product Recommendations component. This component is injected into, say, the Catalog app.
In such a case, it would be prudent to create another micro app called Recommendations and dynamically import it into the Catalog app. This would allow for true, federated, micro-app pattern architecture.
Figure 5.5 – Tree of remote apps with Module Federation
As you can see from the preceding diagram, we can further break down our Catalog and Checkout apps into smaller organism-level components and have each of them load into the Catalog app remotely...
