When a project grows and several business entities can be distinguished (personal account, profile, promo campaigns), can they be split into separate repositories and connected as micro frontends?

Yes, as the project grows and multiple business entities are distinguished (for example, personal account, profile, promotions), it makes sense to split the frontend into separate repositories and connect them as micro frontends.

This allows:

• To divide responsibility and simplify support for each module.
• To develop teams working on different parts in parallel.
• To update and deploy parts of the application independently.

Different approaches can be used to implement micro frontends:

• Web Components — a standardized way to create isolated components.
• Module Federation (Webpack 5) — allows dynamically loading modules from different builds.
• iframe — isolates the environment but makes it more complex to integrate styles and interactions.

It is important to consider:

• Consistency of UI/UX between micro frontends.
• Common libraries and styles to avoid duplication.
• Routing mechanisms and data exchange between micro frontends.

Thus, splitting into micro frontends with separate repositories is a modern and effective approach for scalable projects, provided that the integration and communication between parts are properly organized.