ApsaraMQ for RocketMQ provides multiple instance types that differ in features and specifications. This article compares the instance types and describes the specifications of each type, including compute specifications, Internet bandwidth, and control plane resource quotas, to help you purchase the instance that fits your business requirements.
Instance series
ApsaraMQ for RocketMQ instances belong to one of two series: the Serverless series or the non-Serverless series. The Serverless series includes the Shared type and the Dedicated type. The non-Serverless series includes the Standard edition, the Professional edition, and the Platinum edition. The following figure shows the instance series.
Instances of the Serverless series and the non-Serverless series cannot be converted to each other. Choose the series carefully before you purchase an instance.
For instances of the non-Serverless series, you can switch the billing method from pay-as-you-go to subscription. For more information, seeChange from pay-as-you-go to subscription.
For instances of the non-Serverless series, edition changes are one-way only: you can upgrade, but you cannot downgrade. The upgrade path is Standard edition > Professional edition > Platinum edition.
Instance feature comparison
The following tables compare the features of the instance types in each series.
Serverless series instances
| Item | Shared (by cumulative usage) | Shared (reserved and elastic) | Dedicated (reserved and elastic) |
| Billing method | Pay by cumulative usage | Reserved + Elastic | Reserved + Elastic |
| Isolation method | Physically shared, logically single-tenant | Physically shared, logically single-tenant | Physically dedicated, with exclusive physical nodes |
| Elasticity |
|
|
|
| Lightweight topic model | Not supported | Not supported | Supported |
| Disaster recovery and high availability |
|
|
|
| Cross-availability zone data replication mode For more information, seeInstance disaster recovery. | Asynchronous replication | Asynchronous replication | Synchronous replication, asynchronous replication |
| Disaster recovery drills | Not supported | Not supported | Supported |
| Maximum message retention period | Maximum: 30 days. Default value: 3 days. | Maximum: 30 days. Default value: 3 days. | Maximum: 30 days. Default value: 3 days. You cansubmit a ticketto customize this value. After customization, the instance cannot be downgraded to another series. |
| Maximum scheduled message duration | Maximum: 7 days | Maximum: 7 days | Maximum: 7 days. You cansubmit a ticketto customize this value. After customization, the instance cannot be downgraded to another series. |
Non-Serverless series (subscription and pay-as-you-go) instances
| Item | Standard edition | Professional edition | Platinum edition |
| Product features | Aligned with open source Apache RocketMQ. Provides the following basic features:
| Provides the following enhanced features on top of the Standard edition:
| Provides the following services on top of the Professional edition:
|
| Lightweight topic model | Supported | Supported | Supported |
Disaster recovery and high availability Note Availability zones are managed by the service and cannot be customized. |
|
|
|
| Cross-availability zone data replication mode For more information, seeInstance disaster recovery. | Asynchronous replication | Asynchronous replication | Synchronous replication, asynchronous replication |
| Isolation method | Physically shared, logically single-tenant | Physically shared, logically single-tenant | Physically dedicated, with exclusive physical nodes |
| Stability SLA |
|
|
|
| Maximum scheduled message duration | Maximum: 7 days | Maximum: 40 days | Maximum: 40 days |
Instance type limits
Instance type limits
Standard Edition, Single Node Edition, and Professional Edition instances do not support elastic TPS. Plan your resource usage in advance to prevent instance throttling if sudden traffic spikes exceed your specification limits.
The topic and group quotas per instance are sufficient for most large-scale production use cases. As a best practice, isolate your business services across different instances based on department or domain. This practice improves stability and resource management.
The message TPS specification is based on the total number of normal messages sent and received, using a standard message size of 4 KB as the benchmark. A multiplier applies when you use advanced message features or send large messages. For details on how TPS is calculated, see Calculation specifications.
If the actual TPS for message sending and receiving exceeds the upper limit of your purchased instance type:
If elastic TPS is enabled, your instance can operate normally as long as the TPS is within the provisioned elastic range. Usage that exceeds the base specification is billed on a pay-as-you-go basis. If the TPS surpasses the maximum elastic capacity, the instance is subject to throttling.
For more information about the billing of elastic TPS for non-Serverless instances, see Elastic TPS Fees. For more information about the billing of elastic TPS for Serverless instances, see Serverless elastic TPS fees.
If your instance does not support elastic TPS or the feature is not enabled, Message Queue for RocketMQ throttles the instance.
ImportantThrottling behavior: When throttling is triggered, the server returns a failure response for requests that exceed the limit. Requests are not queued.
Risk of message loss: Throttling does not discard messages on the server side. However, if the client has no retry mechanism after it receives a throttling failure response, the system does not retain the message. This is equivalent to message loss.
Best practices: Configure a reasonable message send retry policy on the client. This policy handles send failures caused by transient throttling and ensures message reliability.
An excessive number of client connections to a Message Queue for RocketMQ instance consumes significant server resources and can severely impact stability. Therefore, ensure the number of client connections does not exceed the limit for your instance type.
Serverless series instances
Number of concurrent online clients: The total number of online producers and consumers. Each is counted as one client.
Resource count: The total number of topics and consumer groups.
Deployment architecture | Capacity mode | TPS range | Max concurrent clients | Free client quota | Max resource count | Free resource quota | Max LiteTopics |
Shared | Cumulative usage | All | 5,000 | 500 | 3,000 | 100 | / |
Reserved + Elastic | [2,000, 20,000] | 5,000 | 1,000 | 3,000 | 200 | ||
(20,000, 50,000] | 8,000 | 2,000 | 3,000 | 200 | |||
(50,000, 100,000] | 10,000 | 3,000 | 3,000 | 200 | |||
(100,000, 200,000] | 20,000 | 5,000 | 3,000 | 200 | |||
Dedicated | Reserved + Elastic | 5,000 | 3,000 | 2,000 | 3,000 | 300 | 300,000 |
10,000 | 6,000 | 4,000 | 4,000 | 300 | 500,000 | ||
15,000 | 8,000 | 6,000 | 6,000 | 500 | 800,000 | ||
[20,000, 50,000] | 10,000 | 8,000 | 6,000 | 500 | 1,200,000 | ||
(50,000, 100,000] | 20,000 | 10,000 | 6,000 | 500 | 3,000,000 | ||
(100,000, 200,000] | 40,000 | 20,000 | 8,000 | 1,000 | 3,600,000 | ||
(200,000, 300,000] | 80,000 | 40,000 | 10,000 | 1,500 | 5,000,000 | ||
(300,000, 500,000] | 100,000 | 50,000 | 16,000 | 2,000 | 6,500,000 | ||
(500,000, 1,000,000] | 200,000 | 100,000 | 40,000 | 3,000 | 11,600,000 |
Non-Serverless (subscription and pay-as-you-go) instances
Standard edition
Instance sub-series | Instance type | Max base TPS (ops/sec) | Max burst TPS (ops/sec) | Max connections | Egress bandwidth (Mbps) | Free topic quota | Max topic quota | Max consumer groups | Max LiteTopics |
Single Node Edition (No longer sold) | rmq.s1.micro | 500 | Not applicable This instance type does not support burst elasticity. | 2,000 | 1 to 1,000 Customizable. | 100 | 100 | 1,000 | / |
Cluster High-availability Edition | rmq.s2.2xlarge | 2,000 | 4,000 | 300 | 50,000 | ||||
rmq.s2.4xlarge | 4,000 | 4,000 | 150,000 | ||||||
rmq.s2.6xlarge | 6,000 | 6,000 | 500 | 300,000 |
If the topic and consumer group quotas for the top-tier Standard Edition instance (rmq.s2.6xlarge) are insufficient for your business needs, upgrade to the Professional Edition and select a suitable instance type.
Professional edition
Instance sub-series | Instance type | Max base TPS (ops/sec) | Max burst TPS (ops/sec) | Max connections | Egress bandwidth (Mbps) | Free topic quota | Max topic quota | Max consumer groups | Max LiteTopics |
Single Node Edition (No longer sold) | rmq.p1.micro | 500 | Not applicable This instance type does not support burst elasticity. | 2,000 | 1 to 1,000 Customizable. | 150 | 150 | 1,500 | / |
Cluster High-availability Edition | rmq.p2.4xlarge | 4,000 | 2,000 | 4,000 | 500 | 2,000 | 150,000 | ||
rmq.p2.6xlarge | 6,000 | 3,000 | 6,000 | 300,000 | |||||
rmq.p2.10xlarge | 10,000 | 5,000 | 10,000 | 1,000 | 500,000 | ||||
rmq.p2.20xlarge | 20,000 | 10,000 | 10,000 | 800,000 | |||||
rmq.p2.30xlarge | 30,000 | 15,000 | 12,000 | 2,000 | 1,000,000 | ||||
rmq.p2.40xlarge | 40,000 | 20,000 | 12,000 | 1,200,000 | |||||
rmq.p2.50xlarge | 50,000 | 20,000 | 14,000 | 1,400,000 | |||||
rmq.p2.100xlarge | 100,000 | 30,000 | 26,000 | 2,200,000 | |||||
rmq.p2.120xlarge | 120,000 | 40,000 | 30,000 | 2,700,000 | |||||
rmq.p2.150xlarge | 150,000 | 50,000 | 38,000 | 3,300,000 | |||||
rmq.p2.200xlarge | 200,000 | 60,000 | 50,000 | 4,500,000 |
If the topic and consumer group quotas for Professional Edition instances of rmq.p2.10xlarge or higher are insufficient for your business needs, submit a ticket.
Platinum edition
Instance sub-series | Instance type | Max base TPS (ops/sec) | Max burst TPS (ops/sec) | Max connections | Egress bandwidth (Mbps) | Free topic quota | Max topic quota | Max consumer groups | Max LiteTopics |
Cluster High-availability Edition | rmq.u2.10xlarge | 10,000 | 5,000 | 10,000 | 1 to 1,000 Customizable. | 200 | 3,000 | 4,000 | 600,000 |
rmq.u2.20xlarge | 20,000 | 10,000 | 10,000 | 800,000 | |||||
rmq.u2.30xlarge | 30,000 | 15,000 | 12,000 | 1,000,000 | |||||
rmq.u2.40xlarge | 40,000 | 20,000 | 10,000 | 1,200,000 | |||||
rmq.u2.50xlarge | 50,000 | 20,000 | 14,000 | 1,400,000 | |||||
rmq.u2.60xlarge | 60,000 | 22,000 | 16,000 | 1,600,000 | |||||
rmq.u2.70xlarge | 70,000 | 24,000 | 18,000 | 1,700,000 | |||||
rmq.u2.80xlarge | 80,000 | 26,000 | 20,000 | 1,800,000 | |||||
rmq.u2.90xlarge | 90,000 | 28,000 | 24,000 | 2,000,000 | |||||
rmq.u2.100xlarge | 100,000 | 30,000 | 26,000 | 2,200,000 | |||||
rmq.u2.120xlarge | 120,000 | 40,000 | 30,000 | 2,700,000 | |||||
rmq.u2.150xlarge | 150,000 | 50,000 | 38,000 | 3,300,000 | |||||
rmq.u2.200xlarge | 200,000 | 60,000 | 50,000 | 4,500,000 | |||||
rmq.u2.250xlarge | 250,000 | 70,000 | 51,000 | 5,600,000 | |||||
rmq.u2.300xlarge | 300,000 | 80,000 | 52,000 | 6,300,000 | |||||
rmq.u2.350xlarge | 350,000 | 90,000 | 53,000 | 7,500,000 | |||||
rmq.u2.400xlarge | 400,000 | 100,000 | 54,000 | 9,300,000 | |||||
rmq.u2.450xlarge | 450,000 | 120,000 | 60,000 | 10,400,000 | |||||
rmq.u2.500xlarge | 500,000 | 140,000 | 66,000 | 11,600,000 | |||||
rmq.u2.550xlarge | 550,000 | 160,000 | 72,000 | 12,800,000 | |||||
rmq.u2.600xlarge | 600,000 | 200,000 | 80,000 | 14,000,000 | |||||
rmq.u2.1000xlarge | 1,000,000 | 300,000 | 134,000 | 23,200,000 |
If the topic and consumer group quotas for Platinum Edition instances are still insufficient for your business needs, submit a ticket.
Domestic localization support
ApsaraMQ for RocketMQ supports Hygon processors to meet domestic localization requirements.
Next steps
For the billable items and billing details of subscription and pay-as-you-go instances, seeBilling for subscription and pay-as-you-go instances.
For the billable items and billing details of Serverless instances, seeBilling for existing Standard and Professional serverless instances.