You can configure data outbound rules of Message Queue for MQTT to export data from Message Queue for MQTT to other Alibaba Cloud services. This topic describes the working mechanism, scenarios, and limits of exporting data from Message Queue for MQTT to other Alibaba Cloud services. This topic also describes the resource mappings between Message Queue for MQTT and other Alibaba Cloud services.
Working mechanism

Scenarios
Client data reporting
A large number of clients report their status data to Message Queue for MQTT by using the MQTT protocol. After you configure a data outbound rule to map the topics of Message Queue for MQTT and the topics of Message Queue for Apache RocketMQ, you can start the consumers of Message Queue for Apache RocketMQ in the backend service application to process the reported data.
Limits
- You can export data only from Message Queue for MQTT to Message Queue for Apache RocketMQ.
Resource mapping methods
Message Queue for MQTT supports multi-level topics, whereas Message Queue for Apache RocketMQ supports single-level topics. Therefore, when a data outbound rule is used to map resources, a level-1 topic in Message Queue for MQTT is mapped to a topic in Message Queue for Apache RocketMQ, and data in the level-1 topic in Message Queue for MQTT is exported to the Message Queue for Apache RocketMQ topic. Level-2 and level-3 topics in Message Queue for MQTT are mapped to the message properties in Message Queue for Apache RocketMQ.
Message Queue for MQTT resource | Alibaba Cloud service | Resource of the Alibaba Cloud service | Property mappings |
---|---|---|---|
Topics of Message Queue for MQTT | Message Queue for Apache RocketMQ | Topics of Message Queue for Apache RocketMQ | Message structure mappings between Message Queue for MQTT and Message Queue for Apache RocketMQ |
References
For more information about console operations, see Manage data outbound rules.