Data outbound rules forward messages from ApsaraMQ for MQTT clients to other Alibaba Cloud services, enabling your backend applications to consume MQTT messages through the destination service's API without connecting directly to the MQTT broker.
How it works
Each data outbound rule defines a mapping between an ApsaraMQ for MQTT parent topic and a resource in a destination Alibaba Cloud service. After you activate a rule, every message published to the mapped parent topic is automatically forwarded to the destination.
Use cases
Client data reporting
When a large number of devices report status data over the MQTT protocol, use a data outbound rule to route the messages to ApsaraMQ for RocketMQ for backend processing:
Map an ApsaraMQ for MQTT parent topic to an ApsaraMQ for RocketMQ topic through a data outbound rule.
Start consumers in your backend service to read from the RocketMQ topic and process the incoming data.
Limitations
Item | Limit | Details |
Rules per instance | 100 | To request a higher quota, join DingTalk group 116015007918 and contact the ApsaraMQ for MQTT technical support team. |
Rule deduplication | One rule of the same type per internal resource | Each group ID supports one client status notification rule. Each ApsaraMQ for MQTT topic supports one data inbound rule and one data outbound rule. |
Region | Same-region only | The data source and data destination must reside in the same region. For example, if the data source is an ApsaraMQ for MQTT instance in the China (Hangzhou) region, the destination must also be in the China (Hangzhou) region. |
ApsaraMQ for MQTT instance version | Kernel version V3.x.x | View the kernel version from the instance list or the Instance Details page in the ApsaraMQ for MQTT console. |
ApsaraMQ for RocketMQ instance version | ApsaraMQ for RocketMQ 4.0 only | Data inbound rules and data outbound rules support only ApsaraMQ for RocketMQ 4.0 instances. |
Topic mapping
Data outbound rules map at the parent topic level. All messages published to a given parent topic on ApsaraMQ for MQTT are exported to the corresponding resource in the destination service. Subtopics on ApsaraMQ for MQTT are mapped to message properties in ApsaraMQ for RocketMQ.
The following table lists the supported resource mappings:
ApsaraMQ for MQTT resource | Destination service | Destination resource | Message structure reference |
Topics | ApsaraMQ for RocketMQ | Topics | Message structure mappings between ApsaraMQ for MQTT and ApsaraMQ for RocketMQ |
What's next
Manage data outbound rules: Create, modify, and delete rules in the console.
Message structure mappings between ApsaraMQ for MQTT and ApsaraMQ for RocketMQ: Learn how MQTT message fields map to RocketMQ message fields.