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

Resource support

ApsaraMQ for RabbitMQ is compatible with all components of open source RabbitMQ.

  • Queue: stores messages. Clustering consumption is supported.
    Note ApsaraMQ for RabbitMQ does not support priority-based message processing. The priorities of queues you declare by using the optional queue parameter x-max-priority do not take effect.
  • Exchange: routes messages to one or more queues based on routing rules and discards the messages that do not comply with routing rules.
  • vhost: isolates resources to meet requirements such as the isolation of production and test environments, and business splitting.

O&M support

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

  • Monitoring and alerting tool: monitors online connections, message accumulation, and delayed delivery in real time to detect issues in a timely manner.
  • Resource reporting tool: allows you to query devices, group and manage online devices, and collect statistics on the sending and receiving of messages.
  • OpenAPI (RESTful): provides flexible and convenient self-service resource management, self-service O&M, and RESTful APIs.

Message types

ApsaraMQ for RabbitMQ supports the following message types:

  • Common message: a message that is immediately sent to consumers by the broker.
  • Delayed message: a message that is sent to consumers by the broker after a specified period of time. This type of message applies to scenarios in which a time window is required for message consumption.
Note ApsaraMQ for RabbitMQ does not support transactional messages. That is, transactional operations, such as the txSelect, txCommit, and txRollback commands, in AMQP 0-9-1 are not supported. To be compatible with these transactional operations, after the ApsaraMQ for RabbitMQ broker receives the commands, it directly returns success. However, the commands actually do not take effect.