Micro Frontend Chunk Redeployment via Unified Repository

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In micro frontend frameworks, every change or fix requires a complete application build redeployment, which is inefficient and requires managing separate repositories for multiple clients.

Innovation Solution

A system and method for redeploying specific chunks of an existing application build, allowing users to deploy small features independently without redeploying the entire application, using a single repository to manage changes across all clients.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a complete application build is deployed every time to fix anything in the application, then the application can be updated with fixes, but the deployment time and resources increase significantly

Engineering Contradiction:

Improveapplication fix deploymentVSAvoiddeployment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent divides the application build into separate chunks or modules that can be deployed independently. Instead of deploying the complete application build, only the specific chunk containing the fix is deployed. This segmentation allows for faster, more efficient updates while maintaining the ability to fix issues in the application.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If separate repositories are managed for multiple clients, then each client's code can be managed independently, but the complexity of repository management increases

Engineering Contradiction:

Improveclient-specific code managementVSAvoidrepository management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple client-specific repositories into a single unified repository structure. The build chunk is generated once and can be deployed to multiple clients simultaneously, eliminating the need to manage separate repositories for each client while still allowing client-specific customization through the module approach.

Inventive Principle:

Principle #5Merging (Combining)

3Productivity

If a complete build is deployed for every feature deployment, then the feature can be deployed, but the deployment process becomes inefficient and time-consuming

Engineering Contradiction:

Improvefeature deployment efficiencyVSAvoiddeployment time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent extracts the specific feature or fix from the complete application build and deploys only that extracted portion. This is achieved through the module approach where individual features are packaged as separate build chunks that can be deployed independently, saving time and resources by avoiding the deployment of unnecessary code.

Inventive Principle:

Principle #2Taking out (Extraction)

4Reliability

If code fixes are deployed in all repositories of all clients, then all clients receive the fix, but the deployment overhead and time increase

Engineering Contradiction:

Improvecode fix distributionVSAvoiddeployment efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent creates a universal build chunk that can be deployed to multiple clients simultaneously. The module-based approach allows a single fix or feature to be packaged once and distributed to multiple clients through the unified repository structure, maintaining the ability to reach all clients while significantly improving deployment efficiency.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS12327109B2Micro frontend framework for redeployment of specific chunks of existing application build

Publication Date: 2025.06.10 RAKUTEN SYMPHONY INC

AI summary

Embodiments herein provide a method for handling redeployment of an existing application build. The method includes receiving a build creation command message for redeployment of the existing application build. Further, the method includes determining availability of a module input, a client input, a workspace input, and an application input in the build creation command message. Further, the method includes determining specific chunks of the existing application build for redeployment based on the module input, the client input, the workspace input, and the application input available in the build creation command message. Further, the method includes redeploying the specific chunks of the existing application build.