Overview

ApsaraMQ for RabbitMQ is a messaging service that is developed based on highly available distributed storage. This service supports the AMQP 0-9-1 protocol. ApsaraMQ for RabbitMQ is compatible with open source RabbitMQ clients. This service prevents various issues, such as message accumulation and split-brain, that occur in open source RabbitMQ and decrease the stability of your business. This service also provides common benefits of cloud messaging services, such as high concurrency, a distributed architecture, and auto scaling.

Benefits

Compatibility with open source RabbitMQ clients

ApsaraMQ for RabbitMQ supports the AMQP 0-9-1 protocol and is compatible with the open source RabbitMQ clients that are developed by using all languages. This service supports queues, exchanges, and virtual hosts that are created in open source RabbitMQ.

Elimination of pain points in open source RabbitMQ

ApsaraMQ for RabbitMQ supports the accumulation of a large number of messages. This prevents breakdowns that can occur if a large amount of memory is consumed when a large number of messages are accumulated. An ApsaraMQ for RabbitMQ cluster uses a distributed architecture that does not support primary nodes. This prevents the split-brain issue that can occur in open source RabbitMQ. This service is highly scalable and supports auto scaling. Each queue supports unlimited throughput.

High performance

ApsaraMQ for RabbitMQ supports millions of queues. Each queue supports scale-out operations and an unlimited number of concurrent requests. This service is highly scalable. The maximum TPS of a queue increases linearly with the number of nodes in the queue. Auto scaling is performed based on your business requirements and is transparent to users. An ApsaraMQ for RabbitMQ cluster provides high performance even if a large number of messages are accumulated.

Advanced features

You can use the global message routing feature in the same manner in which you use Shovel. This feature is stable and reliable, and can be used to forward messages from a queue to another queue or an exchange in a few clicks. The source and the destination can belong to different instances or regions. After the number of retries for consuming a message exceeds the specified threshold value, the message enters the dead-letter queue. This mechanism prevents the issue in which the system cannot consume new messages when a single message cannot be consumed.

Features

Fully Compatible with Open Source RabbitMQ

Queue Allows you to store messages in queues and provides partitions to store messages. A consumer can consume messages by cluster. Exchange Allows you to bind exchanges to queues and specify binding keys. This way, an exchange can filter messages that match specific routing rules and route the messages to one or more queues. The exchange can also drop messages that do not match the rules. Virtual Host (vHost) Uses vHosts to meet isolation requirements, such as production and testing isolation and service splitting.

Various Types of Exchanges

Fanout Exchange Routes messages to all the queues where the current exchange is bound Direct Exchange Routes a message to the queue whose binding key is the same as the routing key of the message Topic Exchange Routes a message to one or more queues based on the fuzzy match result between the routing key of the message and the binding keys of the current exchange

Complete O&M Tools

A series of complete, convenient, and easy-to-use O&M tools to help you identify and resolve issues Monitoring and Alerting Monitors active connections, message accumulation, and delayed message delivery to help you identify issues promptly Resource Reports Allows you to query devices, manage devices by group, and collect statistics on received and sent messages RESTful APIs Provides self-service resource management, self-service O&M, and RESTful APIs