Private Micro Frontends With API-Based Static Code Publishing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current micro frontend (MFE) development approaches lead to performance latency, code redundancy, increased code size, and resource inefficiencies, particularly in static web applications, due to containerization and excess Java code creation, resulting in scalability issues and prolonged deployment times.

Innovation Solution

A private web-based application utilizing non-containerized micro frontends (MFEs) with unique URLs, accessed through API requests, is deployed and managed efficiently, using a consolidated enterprise application with a hosting server and object storage like Amazon S3, minimizing resource usage and enabling scalable deployment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If micro frontends are containerized using React.js and Spring Boot, then each micro frontend can be independently deployed, but excess Java code and RAM/CPU resources are consumed

Engineering Contradiction:

Improveindependent deployment capabilityVSAvoidcode size and resource consumption

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts the essential micro frontend functionality from the containerized architecture, keeping only the necessary JavaScript/TypeScript code while removing the excess Java backend infrastructure. This allows independent deployment of MFEs as static web assets without requiring full Spring Boot containers, thereby reducing code size and resource consumption while maintaining independent deployment capability.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent adopts a lightweight, disposable approach to MFE deployment by using static web assets that can be quickly served and replaced. Instead of maintaining heavy Java containers, the system uses simple HTML/JS/CSS files that can be rapidly deployed and updated, reducing both the cost and complexity of each deployment unit.

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

2Adaptability or versatility

If the application is split into multiple micro frontends, then scalability is improved, but deployment time increases due to containerization overhead

Engineering Contradiction:

ImprovescalabilityVSAvoiddeployment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the application into multiple independent micro frontends that can be developed, built, and deployed separately. Each MFE is a self-contained unit with its own codebase and dependencies, allowing parallel development and independent deployment. This segmentation enables scalability while reducing deployment time compared to monolithic containerized approaches.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by pre-bundling each micro frontend's dependencies and assets during the build process. This allows the MFEs to be deployed as complete, self-contained units without requiring runtime container initialization, thereby reducing deployment time while maintaining the scalability benefits of multiple independent frontends.

Inventive Principle:

Principle #10Preliminary action

3Ease of manufacture

If an integrated frontend application is used, then the architecture is simple to maintain, but revising the architecture becomes difficult

Engineering Contradiction:

Improveinitial development simplicityVSAvoidarchitectural flexibility

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent divides the integrated frontend into multiple independent micro frontend modules, each responsible for specific functionality. This segmentation maintains initial development simplicity through clear module boundaries while enabling architectural flexibility by allowing individual modules to be revised, replaced, or reorganized without affecting the entire application.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements a universal module system where each micro frontend follows standardized conventions for routing, state management, and dependencies. This universality allows different MFEs to be developed independently using the same patterns while maintaining overall architectural coherence, thus preserving ease of manufacture while enhancing adaptability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250373678A1Private micro frontends with API access to code artifacts in a software repository

Publication Date: 2025.12.04 JPMORGAN CHASE BANK NA

AI summary

An apparatus is provided including storage encoded computer executable code for a consolidated enterprise application configured to provide, to a select set of users with credentialed private access to the consolidated enterprise application, web-based access in a form of a given user experience. In select embodiments, the given user experience involves providing access to user interface static content. The consolidated enterprise application comprises plural frontend web-based independent user interface (UI) unit applications. More specifically, the UI unit applications are individual uncontainerized micro frontends. One or more content publishing interfaces may be provided, that are configured to publish content including the code to a web service storage. The one or more content publishing interfaces are configured to use application programming interface requests to publish the content to the web service storage.