Micro Frontend is an architectural pattern that decomposes a frontend application into independent, autonomous modules, each responsible for a specific functionality. These micro frontends can be developed and deployed independently, enabling teams to work autonomously and choose technologies that suit their needs. The approach promotes scalability, flexibility, and faster development cycles by allowing isolated, incremental updates to specific features. Integration strategies, such as run-time composition, are employed to bring together these modular components into a cohesive user experience.
For a deeper understanding of related key concepts, please explore the Concepts section.
Micro Frontend orchestration refers to the process of coordinating and integrating multiple independent micro frontend modules to create a unified, seamless user experience within a web application. In a Micro Frontend architecture, where different teams may develop and deploy distinct micro frontends independently, orchestration becomes crucial to ensure a cohesive presentation to end-users.
IN SHORT: Orchestration is on top of the composition
Fusionize is a Micro Frontend (MFE) orchestration platform designed to streamline the deployment, management, and configuration of Micro Frontends. The core components of the platform include projects and micro-frontends. A project represents a web application formed by combining multiple micro frontends. An installation defines the Micro Frontends that have been installed on a project, providing essential configurations and specifying conditions that must be met for the mounting of that Micro Frontend.
Whenever a micro frontend is deployed to the Fusionize Content Delivery Network (CDN), a public distribution tag for that specific version becomes accessible. This tag can then be utilized in an installation record to register the micro frontend distribution on a project. While the distribution tag is public, the installation process incorporates authorization measures.
It’s important to note that, in adherence to standard frontend security practices, sensitive information such as passwords, keys, or Protected Personal Information (PPI) should never be included in the deployed distribution.