Runtime Integration of Micro Frontends

The MFEs architecture naturally emerges from component-driven development, as both share the same goal of enabling autonomous teams to develop loosely-coupled, and highly maintainable codebases, and to deliver features quickly and independently.

A micro frontend component is an app component that can be consumed by other apps, during runtime. This is primarily achieved by modifying the generated bundle of the remote and host app components, in order to include the necessary runtime integration code, and to dedupe shared assets and dependencies.

Since app components are just like regular components, only with additional (deployable) artifacts, the choice between runtime and build-time integration is up to you. The same component can be integrated as a Micro Frontend, at runtime, in one app, and as a regular dependency, at build-time, in another.

Standardized development

Using shared envs, the development and build process is consistent across all components, and across all MFEs. Shared envs allow you to enjoy autonomous development, while preserving the same level of quality and consistency across all components.

Consistent UI/UX

Since MFEs are often built using the same Bit components, the same "look and feel" is preserved across all apps. Changes to these components are automatically propagated to all MFEs, and can be easily tested and verified.