Micro Frontend Fragment Governance Without a Shell Application
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional shell applications lack flexibility and cause significant time delays due to their static design and the need for individual start-up processes of content applications, leading to user frustration and inefficiencies as projects grow in complexity.
Innovation Solution
A Micro Frontend (MFE) service platform that hosts a function toggle repository, enabling direct loading of micro frontends on the browser, eliminating the need for a shell application, and providing governance through a service platform with features like user authentication, reverse proxy services, and a function toggle repository for flexible and scalable micro frontend fragment management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a shell application is used to provide governance and launch applications, then governance and security are improved, but flexibility and adaptability deteriorate
Solution Approach 1:
The patent extracts the governance functionality from the traditional shell application and places it in a dedicated governance service. This allows the shell to be removed entirely, enabling each micro-frontend to load independently while the governance service provides necessary security and coordination functions through API calls.
Solution Approach 2:
The system segments the monolithic shell application into independent micro-frontend components. Each micro-frontend is a separate, self-contained unit that can be developed, deployed, and loaded independently, eliminating the need for a unified shell while maintaining governance through service-based coordination.
2Ease of manufacture
If a shell application is used to load micro frontends, then content injection is improved, but loading time and user experience deteriorate
Solution Approach 1:
The patent removes the shell application entirely from the loading process. Instead of the shell loading and then injecting content, micro-frontends load directly in the browser through independent HTTP requests, eliminating the sequential dependency and reducing overall loading time.
Solution Approach 2:
The system performs preliminary actions by pre-bundling micro-frontend content with their routing information in a manifest file. This allows the browser to efficiently load and execute micro-frontends without waiting for shell processing, as the routing and loading instructions are prepared in advance.
3Stability of the object's composition
If a shell application is used to provide a framework, then structure is improved, but complexity and maintenance burden increase
Solution Approach 1:
The patent extracts the framework functionality from the shell application and redistributes it across individual micro-frontend components. Each micro-frontend contains its own framework and dependencies, eliminating the need for a complex unified shell while maintaining structural integrity through standardized interfaces and governance services.
Data Source
AI summary
Systems and methods for a frontend architecture that comprise a service platform that hosts a function toggle repository. The function toggle repository selects specific micro frontend fragments for specific applications. That is, the service platform may determine a particular set of functions to be performed and in turn selects the micro frontend fragments that service that function set. As the function toggle repository may select specific micro frontend fragments for specific applications at runtime and thus provide the needed governance, all new micro frontend fragments and their associated application programming interfaces (APIs) may be onboarded immediately.