Shell-Free Micro Frontend Architecture for Dynamic Application Launch
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional shell applications lack flexibility and cause significant time delays due to static design and individual start-up processes of content applications, leading to user frustration.
Innovation Solution
A novel frontend architecture that hosts multiple capabilities without a shell application, allowing dynamic selection of micro frontend fragments at runtime and linking their start-up procedures with the application's, thereby eliminating serial start-up delays.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a shell application is used to provide governance and capabilities, then application governance and security are improved, but flexibility and adaptability deteriorate
Solution Approach 1:
The patent extracts the shell application layer from the system architecture. Instead of using a traditional shell app to provide governance and capabilities, the invention allows micro-frontend applications to operate independently without being embedded in a shell application, thereby removing the flexibility constraints while maintaining governance through alternative means.
Solution Approach 2:
The patent segments the monolithic shell application structure into independent micro-frontend applications. Each micro-frontend can be developed, deployed, and executed independently, allowing different teams to work on different functionalities without affecting others, thus improving both flexibility and adaptability while maintaining governance through standardized interfaces.
2Speed
If a shell application is used to host content applications, then application launch is improved, but individual content application start-up processes create time delays
Solution Approach 1:
The patent implements preliminary action by pre-loading and caching the shell application and its dependencies in advance. The shell application is prepared and ready to immediately host micro-frontend applications, eliminating the need for repeated initialization. This allows content applications to start up faster since the hosting environment is already prepared.
Solution Approach 2:
The patent merges the start-up processes of the shell application and micro-frontend applications by allowing the shell to initialize once and then dynamically load multiple micro-frontend applications. This combines the initialization overhead into a single operation rather than requiring each content application to perform its own start-up sequence, thereby reducing total start-up time.
3Stability of the object's composition
If the same shell application is used across multiple projects, then consistency is improved, but modifications to support new functionalities cause corruption of other features
Solution Approach 1:
The patent segments the monolithic shell application into independent micro-frontend applications, allowing each project to have its own customized micro-frontend while sharing a common shell infrastructure. This enables modifications to individual micro-frontends without affecting other projects, maintaining consistency at the shell level while allowing adaptability at the micro-frontend level.
Solution Approach 2:
The patent applies local quality by allowing each micro-frontend application to have its own specific functionalities and customizations while maintaining a consistent shell application framework. Each micro-frontend can be modified independently to support project-specific requirements without corrupting other features, as changes are localized to individual micro-frontends rather than affecting the entire shell application.
Data Source
AI summary
Systems and methods for a frontend architecture that comprise a first application that hosts a plurality of functions. The plurality of functions selects specific micro frontend fragments for specific applications. As the plurality of functions 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 APIs may be onboarded immediately.