ApsaraMQ for MQTT V3.x.x does not depend on ApsaraMQ for RocketMQ for data storage. Therefore, the messaging process in ApsaraMQ for MQTT V3.x.x is different from the messaging process in ApsaraMQ for MQTT V2.x.x.
ApsaraMQ for MQTT V2.x.x depends on ApsaraMQ for RocketMQ for message storage. Messages in ApsaraMQ for MQTT are interconnected with messages in ApsaraMQ for RocketMQ. After you create a topic, you can use the SDKs of ApsaraMQ for RocketMQ and ApsaraMQ for MQTT for data exchange.
Due to independent data storage in ApsaraMQ for MQTT V3.x.x, you no longer need to bind an ApsaraMQ for MQTT instance to another service before you use the instance to send and receive messages. To exchange data between ApsaraMQ for MQTT V3.x.x and ApsaraMQ for RocketMQ, you must configure data forwarding rules. The following table describes the differences between the messaging process in ApsaraMQ for MQTT V2.x.x and the messaging process in ApsaraMQ for MQTT V3.x.x in specific scenarios.
Scenario | V2.x.x usage instruction | V3.x.x usage instruction |
Send and receive messages by using an ApsaraMQ for MQTT client | Create a topic in the ApsaraMQ for RocketMQ console or by calling the corresponding API operation and then use the topic to send and receive messages. | Create a topic in the ApsaraMQ for MQTT console and then use the topic to send and receive messages. |
Send messages by using an ApsaraMQ for MQTT client and receive messages by using an ApsaraMQ for RocketMQ client |
|
|
Send messages by using an ApsaraMQ for RocketMQ client and receive messages by using an ApsaraMQ for MQTT client |
|
|
Receive and process client status notifications by using an ApsaraMQ for RocketMQ client when the status of an ApsaraMQ for MQTT client changes |
|
|