Dynamic Micro-Frontend Orchestration for Modular UI Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing user interface (UI) creation methods are time-consuming due to manual coding and lack modularity, agility, and efficiency in integrating content from multiple providers.

Innovation Solution

A method and apparatus for UI generation using micro-frontends, where each micro-frontend provides content to a graphical user interface (GUI) through a backend orchestrator service, allowing configuration data to be read and used to generate a UI definition file, which includes identification, size, and position information, and publishes the GUI dynamically.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual coding is used to create user interfaces, then developers have full control over UI creation, but the process becomes time-consuming and less efficient

Engineering Contradiction:
ImproveUI generation efficiencyVSAvoidTime required for manual coding
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the user interface into multiple independent micro-frontends, each developed and configured separately. This segmentation enables parallel development and reduces the time required for manual coding by allowing different teams to work on different UI components simultaneously, directly addressing the productivity-time contradiction.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by pre-configuring micro-frontends with metadata including identification, size, and position information before runtime. The backend orchestrator service pre-processes configuration data from multiple content providers, generating a complete UI definition file in advance, which eliminates the need for time-consuming manual coding during deployment.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If traditional monolithic UI architecture is used, then the system structure is simple, but it lacks modularity and agility in integrating content from multiple providers

Engineering Contradiction:
ImproveModularity and agilityVSAvoidSystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides the monolithic UI architecture into segmented micro-frontends, where each micro-frontend represents an independent, modular unit. This segmentation provides the required modularity and agility by allowing individual micro-frontends to be developed, deployed, and updated independently, while the backend orchestrator manages the overall system integration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a backend orchestrator service as an intermediary between multiple content providers and the user interface. This mediator handles the complexity of integrating content from multiple providers by centralizing the orchestration logic, managing configuration data, and coordinating the assembly of micro-frontends, thus enabling adaptability without proportionally increasing overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If configuration data from multiple micro-frontends is integrated dynamically, then customization and agility are improved, but the complexity of managing configuration data increases

Engineering Contradiction:
ImproveCustomization capabilityVSAvoidConfiguration data management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal configuration data structure that handles multiple micro-frontends from different content providers through a common interface. The backend orchestrator service provides multi-functional capabilities by reading, validating, and integrating configuration data from various sources using the same processing logic, thereby enabling customization without linearly increasing management complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

Each micro-frontend provides self-service by including its own configuration data (identification, size, position) in a standardized format. This self-describing approach allows the backend orchestrator to automatically process and integrate configuration data without requiring complex manual management, enabling high customization capability while keeping configuration management complexity manageable through automation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250231776A1Dynamic interface generation using micro-frontends
Publication Date: 2025.07.17 LENOVO ENTERPRISE SOLUTIONS (SINGAPORE) PTE LTD
  • US20250231776A1 patent drawing
  • US20250231776A1 patent drawing
  • US20250231776A1 patent drawing

AI summary

A method for webpage generation is disclosed. The method includes receiving configuration data from each of a plurality of micro-frontends registered with a backend orchestrator service, each of the plurality of micro-frontends is configured to provide content to be displayed on a graphical user interface (“GUI”). Each micro-frontend is configured to provide content of at least one content type. Each of the plurality of micro-frontends is from a content provider. The method includes reading the configuration data from each of the plurality of micro-frontends. The configuration data of a micro-frontend of the plurality of micro-frontends includes identification of the micro-frontend and size and position information for display on the GUI of the content of the micro-frontend. The method includes generating a UI definition file. The UI definition file includes the configuration data from the plurality of micro-frontends. The method includes publishing the GUI from the UI definition file.