All Products
Search
Document Center

ApsaraMQ for RabbitMQ:Instance editions

Last Updated:Sep 21, 2023

This topic describes the instance editions provided by ApsaraMQ for RabbitMQ.

Description

Table 1. Description of instance editions

Category

Item

Professional Edition

Enterprise Edition

Enterprise Platinum Edition

High availability and reliability

Architecture

Shared instances that provide data persistence. Each instance is logically isolated and has three replicas to ensure high availability.

Shared instances that provide data persistence. Each instance is logically isolated and has three replicas to ensure high availability.

Dedicated instances that provide data instance. Each instance is deployed in a dedicated physical cluster and has three replicas to ensure high availability.

SLA

99.95%

99.95%

99.99%

Functions and features

Data observability and monitoring and alerting

Data can be observed in the ApsaraMQ for RabbitMQ console in real time.

For more information, see Monitoring and alerting.

Managed Service for Prometheus and Managed Service for Grafana are used to provide the dashboard feature. This feature allows you to view the data charts of various fine-grained metrics.

For more information, see Dashboard.

Managed Service for Prometheus and Managed Service for Grafana are used to provide the dashboard feature. This feature allows you to view the data charts of various fine-grained metrics.

For more information, see Dashboard.

Global message routing

Not supported.

Supported.

Supported.

Transport Layer Security (TLS) V1.2 encryption

Not supported.

Supported.

Supported.

Usage limits

Limits on clusters

Limits are imposed on clusters.

For more information, see Limits on clusters.

A larger size of messages can be processed in clusters.

For more information, see Limits on clusters.

Few limits are imposed on clusters.

For more information, see Limits on clusters.

Limits on API calls

Limits are imposed on API calls.

For more information, see Limits on API calls.

Limits are imposed on API calls.

For more information, see Limits on API calls.

No limits are imposed on API calls.

For more information, see Limits on API calls.

Limits on instance editions

Limits on clusters

Item

Professional Edition

Enterprise Edition

Enterprise Platinum Edition

Number of virtual hosts (vhosts) per instance

Valid values: Number of queues to 200.

200

4,096

Number of connections per instance

Equal to the number of queues multiplied by 4.

Valid values: 1000 to 5000.

Purchase a connection quota based on the instance specification.

A free quota of at least 2,000 connections is provided for an instance. The maximum number of connections per instance is 10,000.

Purchase a connection quota based on the instance specification.

A free quota of 50,000 connections is provided for an instance. The maximum number of connections per instance is 100,000.

Number of exchanges per vhost

Equal to the number of queues.

Equal to the number of queues.

None

Number of bindings per vhost

Equal to the number of queues multiplied by 10.

Valid values: 4096 to 20000.

Equal to the number of queues multiplied by 10.

Valid values: 4096 to 20000.

None

Number of queues bound to an exchange

256

256

256

If you want to increase the quota, contact Alibaba Cloud technical support.

Number of consumers per queue

Equal to the number of queues multiplied by 4.

Valid values: 50 to 5000.

Equal to the number of queues multiplied by 4.

Valid values: 800 to 5000.

None

Number of channels per connection

Valid values: 64 and Number of queues.

  • If the number of queues is less than or equal to 64, the number of channels per connection is 64.

  • If the number of queues is greater than 64, the number of channels per connection is equal to the number of queues.

Valid values: Number of queues to 2048.

  • If the number of queues is less than 2,048, the number of channels per connection is equal to the number of queues.

  • If the number of queues is greater than or equal to 2,048, the number of channels per connection is 2048.

3000

Message size

64 KB

1 MB

Note

If a message is smaller than 64 KB in size, one API call is counted to process the message data. If a message is larger than 64 KB in size, one API call is counted to process each 4 KB of the excess message data.

1 MB

Maximum retention period for a delayed message

24 hours

24 hours

7 days

Maximum retention period for a message

3 days

3 days

3 days

Maximum number of times a message can be requeued

16

16

64

Retry interval for time-out messages

60 seconds

5 minutes

30 minutes

Limits on API calls

Item

Operation

Professional Edition

Enterprise Edition

Enterprise Platinum Edition

Synchronous message receiving on an instance

basicGet

500 TPS

500 TPS

None

Queue clearance on an instance

purgeQueue

500 TPS

500 TPS

None

Exchange creation on an instance

exchangeDeclare

500 TPS

500 TPS

None

Exchange deletion on an instance

exchangeDelete

500 TPS

500 TPS

None

Queue creation on an instance

queueDeclare

500 TPS

500 TPS

None

Queue deletion on an instance

queueDelete

500 TPS

500 TPS

None

Binding creation on an instance

queueBind

500 TPS

500 TPS

None

Binding deletion on an instance

queueUnbind

500 TPS

500 TPS

None

Message restoration on an instance

basicRecover

500 TPS

500 TPS

None

Message requeuing on an instance

  • basicReject(requeue=true)

  • basicNack(requeue=true)

20 TPS

20 TPS

None