What is Configuration Upgrade?

Configuration upgrade is an update mechanism where developers independently manage configuration content, primarily used to modify application configuration information without needing to publish the application.

1. Core Concepts

1.1 Configuration

Configuration application upgrade is where the UpgradeLink system maintains an application configuration JSON, eliminating the need for developers to maintain backend configuration services. Simply update it on the UpgradeLink system, and the system will distribute the configuration file content to clients.

2. Typical Workflow

1. Developer Preprocessing: Upload the application's required configurations to the UpgradeLink system;
2. Client Startup/Periodic Trigger: Actively send update requests to obtain system configuration version information;
3. Version Comparison: Compare the local application's current version number with the remote configuration's version number returned by the UpgradeLink system;
4. Branch Judgment: If remote version number > local version number, trigger the update process;
5. Client Local Storage: Store the new version's configuration content locally;
6. New Configuration Usage: After local storage is complete, implement the use of the new configuration according to business processes.

If remote version number ≤ local version number: This indicates the current version is the latest, and no configuration updates are needed.

3. Key Implementation Points

Version Hosting Configuration Specifications

• System Configuration Points: Upload application configurations according to UpgradeLink system's specified format and size limits to ensure file integrity and availability;
• Client Configuration: In the client update module, configure the configuration query API address or unique configuration identifier provided by the UpgradeLink system to ensure the client can normally request and obtain configuration information from the system.

4. Advantages and Features

• Full Process Control: Independently decide release rhythm, version history retention, and update strategies; configuration and distribution are guaranteed by the UpgradeLink system, balancing control and operational convenience;
• Extremely Low Operational Costs: No need to build/maintain any configuration servers; rely on the UpgradeLink system to complete full-link configuration management, significantly reducing operational pressure;
• High Flexibility: Supports phased rollouts (achieved by configuring different distribution scopes in the UpgradeLink system), channel-specific updates (configuring multiple sets of configurations and version information in the system), and emergency hotfixes (quickly update corresponding configurations and versions in the system without adjusting the client);
• Cross-Platform Universal: The same core logic can be adapted to multiple terminals, and the UpgradeLink system uniformly provides cross-terminal compatible configuration distribution links;
• Easy Reuse and Expansion: Core update logic can be encapsulated as a common module; different projects only need to replace it with the corresponding project's "unique configuration application identifier" in the UpgradeLink system to quickly integrate.