After ApsaraMQ for MQTT is upgraded from V2.x.x to V3.x.x, it implements independent data storage and eliminates its messaging dependency on ApsaraMQ for RocketMQ. Therefore, the usage of ApsaraMQ for MQTT instances and topics has changed.
| Resource | V2.x.x usage instructions | V3.x.x usage instructions |
|---|---|---|
| ApsaraMQ for MQTT instance | A ApsaraMQ for MQTT instance of version V2.x.x must be bound to a ApsaraMQ for RocketMQ instance before the instance can work normally. | A ApsaraMQ for MQTT instance of version V3.x.x does not need to be bound to a ApsaraMQ for RocketMQ instance to publish and subscribe to messages. |
| ApsaraMQ for MQTT Topic | Parent topics of a ApsaraMQ for MQTT instance of version V2.x.x are the topics of ApsaraMQ for RocketMQ. You can use the ApsaraMQ for RocketMQ console or call an API to create topics for ApsaraMQ for MQTT. | In ApsaraMQ for MQTT of version V3.x.x, you must use the console of ApsaraMQ for MQTT to create topics. |
| ApsaraMQ for MQTT instance endpoint | An endpoint of a ApsaraMQ for MQTT instance of version V2.x.x must be bound to a ApsaraMQ for RocketMQ instance before you can obtain the endpoint in the ApsaraMQ for MQTT console. | In ApsaraMQ for MQTT of version V2.x.x, you do not need to bind the endpoint to a ApsaraMQ for RocketMQ instance to obtain the endpoint in the ApsaraMQ for MQTT console. |
| ApsaraMQ for MQTT rule | No rules are required. V2.x.x versions of Message Queue for MQTT share topics with ApsaraMQ for RocketMQ. | If you need to exchange data with other Alibaba Cloud services (ApsaraMQ for RocketMQ is supported only), you must create a rule in the ApsaraMQ for MQTT console or ApsaraMQ for MQTT. |
Resource usage is highly related to billing. After the upgrade, Message Queue for MQTT topics of V3.x.x do not incur fees, but the rest billing items remain unchanged. This change saves your cost for the original ApsaraMQ for RocketMQ topics. For more information about the billing methods, see Billing overview.