If you call API operations to create resources, such as topics and groups, in ApsaraMQ for MQTT V2.x.x, the API operations may not work as expected after you upgrade ApsaraMQ for MQTT to V3.x.x. In this case, call the new API operations to initialize resources. The version of an ApsaraMQ for MQTT broker is upgraded only after the broker confirms that the code for API operations is modified.
Process
Perform the following steps to upgrade the code of API operations:
Evaluate the use scenarios and traceability chain of API operations.
Join the DingTalk group 116015007918 to contact ApsaraMQ for MQTT technical support for the migration solution.
Modify the code of API operations based on the instructions in the migration solution before you call the new version of API operations.
Contact the service provider to schedule the upgrade of ApsaraMQ for MQTT.
Complete the upgrade of ApsaraMQ for MQTT.
Confirm whether to delete previous API calls and existing resources based on your business requirements.
To ensure compatibility, make sure that the names of the resources that you create by calling API operations in ApsaraMQ for MQTT V2.x.x and ApsaraMQ for MQTT V3.x.x are the same during dual writes. This prevents messaging errors in production environments.