All Products
Search
Document Center

ApsaraMQ for RabbitMQ:Features

Last Updated:Aug 29, 2025

ApsaraMQ for RabbitMQ is compatible with open source RabbitMQ and provides a comprehensive set of O&M tools.

Resource support

ApsaraMQ for RabbitMQ is compatible with the components of open source RabbitMQ:

  • Queue: Stores messages and supports clustering consumption.

    Note

    Dedicated instances of ApsaraMQ for RabbitMQ support the message priority feature. To enable this feature, submit a ticket. After the feature is enabled, clients can declare priority queues using the x-max-priority parameter. The recommended value range is 1 to 10.

  • Exchange: Routes messages to one or more queues based on routing rules and discards messages that do not match the rules.

  • Vhost: Supports the virtual host feature of open source RabbitMQ to meet isolation requirements for scenarios such as production environments and business segmentation.

O&M support

ApsaraMQ for RabbitMQ provides a comprehensive and easy-to-use set of O&M tools:

  • Monitoring and alerts: Provides real-time monitoring of online connections, message accumulation, and delivery latency to promptly identify issues.

  • Resource reports: Provides features such as device queries, management of online devices by group, and statistics on sent and received messages.

  • OpenAPI (RESTful): Provides flexible features for self-service resource management and O&M based on the RESTful standard.

Message types

ApsaraMQ for RabbitMQ supports the following message types:

  • Normal message: A standard message without special attributes, in contrast to a delayed message.

  • Delayed message: A message that can be consumed only after a specified period. This message type is suitable for scenarios that require a time window.

Note

ApsaraMQ for RabbitMQ does not support transactional messages. This means that transactional operations in the AMQP 0-9-1 protocol, such as the txSelect, txCommit, and txRollback commands, are not supported. To maintain compatibility with these transactional operations, the ApsaraMQ for RabbitMQ server returns a success status after it receives the commands, but the commands have no actual effect.