This topic describes the instance types that ApsaraMQ for RabbitMQ provides.
Instance type description
You can purchase new subscription Professional Edition instances only in the China (Qingdao), China (Hohhot), Japan (Tokyo), and regions. In other regions, you can purchase serverless instances that use reserved and elastic specifications as an alternative. These instances offer better performance and are more cost-effective. Existing Professional Edition instances can still be used to send and receive messages and can be upgraded or downgraded without affecting your regular business operations.
Table 1. Instance type description
Category | Item | Serverless instances | Subscription instances | ||||
Shared | Exclusive | Enterprise Edition | Platinum Edition | Professional Edition | |||
Pay-by-cumulative-usage | Reserved + Elastic | Reserved + Elastic | |||||
Billing | Billing method | You are charged based on the cumulative number of messages sent and received. For more information, see Billing of Serverless instances. | You are charged for the reserved capacity. Usage that exceeds the reserved capacity is billed on a pay-as-you-go basis. For more information, see Billing of Serverless instances. | Subscription (upfront payment) The elastic TPS feature is supported. After you enable this feature, the peak TPS for messaging can be increased beyond the base specification. For more information, see Billing of subscription instances. | |||
High availability and reliability | Elastic capacity limit | Up to 50,000 TPS | 1× the base specification | 1× the base specification, up to 50,000 TPS | 0.5× the base specification | ||
Deployment architecture | Shared instance (logically isolated) | Exclusive instance (dedicated physical cluster) | Shared instance (logically isolated) | Exclusive instance (dedicated physical cluster) | Shared instance (logically isolated) | ||
Service availability | High availability (HA) across multiple zones | ||||||
Data reliability | Triplicate data persistence | ||||||
SLA | 99.95% | 99.95% | 99.95% | 99.95% | 99.99% | 99.95% | |
Features | Dashboard (Prometheus + Grafana) | Supported | Supported | Supported | Support | Supported | Not supported |
Supported | Supported | Supported | Supported | Supported | Not supported | ||
Supports Transport Layer Security (TLS) v1.2 encryption, which allows clients to authenticate servers. | Support | Supported | Supported | Supported | Supported | Not supported | |
Not supported | Not supported | Supported | Not supported | Supported | Not supported | ||
Version management (Lets you customize upgrade and release rules for instance versions) | Not supported | Not supported | Supported | Not supported | Not supported | Not supported | |
Limits on instance types
Cluster limits
Limit item | Serverless instances | Subscription instances | |||
Shared | Dedicated | Enterprise Edition | Platinum Edition | Professional Edition | |
Reserved + Elastic/Pay-by-volume | Reserved + Elastic | ||||
Vhosts per instance | 200 | 2,000 | 200 | 4,096 | 200 |
Exchanges per instance | 6,000 | 10,000 | 6,000 | 80,000 | 6,000 |
Bindings per instance | 20,000 | 20,000 | 20,000 | None | 20,000 |
Queues per instance | 6,000 | 10,000 | 6,000 | 80,000 | 6,000 |
Connections per instance | Maximum connections: 10,000. | Maximum connections: 20,000. | Purchase based on the instance type. Each instance has a free quota of 2,000 connections. The maximum number of connections is 10,000. | Purchase based on the instance type. Each instance has a free quota of 50,000 connections. The maximum number of connections is 100,000. | Equal to the number of queues × 4. The number of connections per instance ranges from 1,000 to 5,000. |
Queues per exchange | 256 | 256 You can submit a ticket to request a custom quota. After customization, the instance cannot be downgraded to a shared cluster. | 256 | 256 To request a custom quota, contact Alibaba Cloud technical support. | 256 |
Consumers per queue | Equal to the number of queues × 4. The number of consumers per queue ranges from 800 to 5,000. | None | Equal to the number of queues × 4. The number of consumers per queue ranges from 800 to 5,000. | None | Equal to the number of queues × 4. The number of consumers per queue ranges from 50 to 5,000. |
Channels per connection | 2,000 | 3,000 | The number of channels per connection is the smaller value of Number of queues and 2,048.
| 3,000 | The number of channels per connection is either 64 or the Number of queues.
|
Message size | 10 MB | 10 MB | 10 MB | 50 MB | 64 KB |
Maximum delay for delayed messages | 7 days | 7 days You can submit a ticket to request a custom quota. After customization, the instance cannot be downgraded to a shared cluster. | 7 days | 7 days To request a custom quota, contact Alibaba Cloud technical support. | 24 hours |
Maximum message retention period | 3 days | 3 days | 3 days | 3 days | 3 days |
Maximum delivery attempts | 16 | 16 | 16 | 64 | 16 |
Maximum: 3 hours Default: 5 minutes | Maximum: 12 hours Default: 30 minutes | Maximum: 3 hours Default: 5 minutes | Maximum: 12 hours Default: 30 minutes | Maximum: 10 minutes Default: 1 minute | |
API call limits
Limit item | API | Serverless instances | Subscription instances | |||
Shared | Dedicated | Enterprise Edition | Platinum Edition | Professional Edition | ||
Reserved + Elastic/Pay-by-volume | Reserved + Elastic | |||||
Synchronously get messages for an instance |
| 500 TPS | None | 500 TPS | ||
Purge a queue for an instance |
| 500 TPS | None | 500 TPS | ||
Create an exchange for an instance |
| 500 TPS | None | 500 TPS | ||
Delete an exchange for an instance |
| 500 TPS | None | 500 TPS | ||
Create a queue for an instance |
| 500 TPS | None | 500 TPS | ||
Delete a queue for an instance |
| 500 TPS | None | 500 TPS | ||
Create a binding for an instance |
| 500 TPS | None | 500 TPS | ||
Delete a binding for an instance |
| 500 TPS | None | 500 TPS | ||
Recover messages for an instance |
| 500 TPS | None | 500 TPS | ||
Requeue messages for an instance |
| 20 TPS | None | 20 TPS | ||