Micro-frontend Internationalization Configuration Centralization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the micro-front-end architecture, each sub-application has its own internationalization file, leading to duplicate configurations and inconsistent translations of the same words across sub-applications, making maintenance cumbersome and inefficient.

Innovation Solution

A micro-front-end-based page internationalization configuration method that creates an internationalized page in the main application, configures it, persists the data, and transmits it to sub-applications for page translation, ensuring unified translations and reducing the need for code modifications and redeployments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If each sub-application has its own internationalization file, then sub-applications can be independently developed and deployed, but duplicate configurations and inconsistent translations occur across sub-applications

Engineering Contradiction:
Improveindependent development and deployment capabilityVSAvoidtranslation consistency
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The patent merges the internationalization configuration management from multiple distributed sub-application files into a single centralized main application file. This allows all sub-applications to share a unified internationalization configuration, ensuring consistent translations across the entire system while maintaining the independent deployment capability of sub-applications through the micro-front-end architecture.

Inventive Principle:
Principle #5Merging (Combining)

2Ease of operation

If internationalization configuration is modified in production environment, then language updates can be applied, but code modification, repackaging, and redeployment are required

Engineering Contradiction:
Improveconfiguration update capabilityVSAvoiddeployment efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent performs preliminary action by establishing a centralized internationalization configuration file in the main application during the development phase. This configuration is persisted and can be dynamically loaded and updated in the production environment without requiring code modifications, repackaging, or redeployment. The configuration file is prepared in advance with all necessary translation data, enabling easy updates by simply replacing the configuration file.

Inventive Principle:
Principle #10Preliminary action

3Manufacturing precision

If a centralized internationalization configuration is used, then translation consistency is improved, but the complexity of data management and transmission increases

Engineering Contradiction:
Improvetranslation consistencyVSAvoidconfiguration management complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent extracts the internationalization configuration data from the complex micro-front-end sub-application structures and consolidates it into a separate, dedicated configuration file in the main application. This extraction simplifies data management by centralizing all translation configurations in one place, reducing the complexity of managing distributed internationalization files across multiple sub-applications.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12223296B2Micro-front-end-based page internationalization configuration method and apparatus, device, and medium
Publication Date: 2025.02.11 INSPUR SUZHOU INTELLIGENT TECH CO LTD
  • US12223296B2 patent drawing
  • US12223296B2 patent drawing
  • US12223296B2 patent drawing

AI summary

The present application relates to the technical field of computers, and discloses a micro-front-end-based page internationalization configuration method and apparatus, a device and a medium. The method includes: creating an internationalized page in a micro-front-end main application, and configuring the internationalized page to obtain a configured internationalized page; persisting data in the configured internationalized page; and reading the data and transmitting the data to at least one micro-front-end sub-application for any one of the micro-front-end sub-applications to perform page translation according to the data.