This topic describes the announcement on upgrading ApsaraMQ for MQTT from V2.x.x to V3.x.x and the procedure changes in using the service after the upgrade.
Announcement
Starting from July 23, 2020, ApsaraMQ for MQTT is available for upgrade from V2.x.x to V3.x.x. The upgrade does not affect messaging on clients. If you have special requirements on the start time and time window of the upgrade, join the DingTalk group 116015007918 to contact ApsaraMQ for MQTT technical support.
Overview
The process for using ApsaraMQ for MQTT changes after the service is upgraded from V2.x.x to V3.x.x. The following figure shows the changes.
Description
Compared with ApsaraMQ for MQTT V2.x.x, ApsaraMQ for MQTT V3.x.x implements independent data storage. After you purchase and activate an ApsaraMQ for MQTT instance, you can create resources without the need to bind the instance to an ApsaraMQ for RocketMQ instance. This reduces usage costs and improves usage efficiency.
In addition, ApsaraMQ for MQTT V3.x.x also abstracts data exchange between ApsaraMQ for MQTT and ApsaraMQ for RocketMQ. You can configure rules to export data from ApsaraMQ for MQTT to other Alibaba Cloud services or import data from other Alibaba Cloud services to ApsaraMQ for MQTT. ApsaraMQ for RocketMQ is one of the Alibaba Cloud services to which data in ApsaraMQ for MQTT can be forwarded.
The following changes are involved in this upgrade:
Resource usage affects the billing of ApsaraMQ for MQTT. After the upgrade, you are not charged for topics in ApsaraMQ for MQTT V3.x.x for now. The other billable items remain unchanged. This saves your costs for the original ApsaraMQ for RocketMQ topics. For more information, see Billing overview.
Changes in the messaging process
If data exchange is required between ApsaraMQ for MQTT and ApsaraMQ for RocketMQ clients, configure the rules based on the description in Changes in the messaging process.
You must modify the code in the API operations based on the description in Changes in API operations.