The real-time publishing platform includes a client SDK that you can use to easily integrate real-time publishing capabilities into your client.
The real-time publishing flow is as follows:
Add the corresponding SDK to the client to integrate real-time upgrade, hotpatching, or H5 offline package capabilities.
Package version upgrade packages, hotpatching packages, and offline packages in the mPaaS plugin and upload them to the publishing console.
Create publishing tasks in the console for phased releases and official releases.
The client then pulls the new deployment packages for upgrades, hotpatching, and offline publishing.
You can also use the switch configuration service to modify the client's code logic. Add the required switch configuration items in the console to deliver them to specific targets.
Workflow
The following chart shows the workflow for the real-time publishing of version upgrade packages, hotpatching packages, and offline packages:
Console management
You can perform the following operations in the real-time publishing console:
Version upgrade package > Release management: Manage configurations for publishing new client versions.
Hotpatching package > Hotpatching management: Fix online bugs without releasing a new version.
Offline package > Offline package management: Package various services into offline packages and deliver them through the publishing platform to update client resources.
Switch configuration > Configuration management: Configure, modify, and push various switches, and deliver them to specific targets based on criteria such as platform, whitelist, and percentage.
Whitelist management: Manage whitelists for real-time publishing. You can easily create whitelists with hundreds of thousands of entries for publishing tasks.
Publishing rule management: Predefine configuration data for real-time publishing to avoid manual input, improve efficiency, and reduce errors.