This topic describes the instance types that ApsaraMQ for RocketMQ supports, the differences between them, and their specifications. Specifications include computing power, Internet bandwidth, and resource quotas. This information helps you choose an instance that meets your business needs.
Instance series
You cannot convert an instance between the Serverless and non-Serverless series. Therefore, you must choose the series carefully before you make a purchase.
For non-Serverless series instances, you can change the billing method from pay-as-you-go to subscription. For more information, see Change from pay-as-you-go to subscription.
For non-Serverless series instances, you can only upgrade the instance series. Downgrades are not supported. The upgrade path is: Standard Edition > Professional Edition > Platinum Edition.
Instance feature comparison
Serverless series instances
Comparison item | Shared | Dedicated | |
By cumulative usage | Reserved + Elastic | Reserved + Elastic | |
Deployment method | Physically shared. Logically single-tenant. | Physically shared. Logically single-tenant. | Physically dedicated. Occupies dedicated physical nodes. |
Billing method | Pay-by-cumulative-usage | Reserved + Elastic | Reserved + Elastic |
Elasticity |
|
|
|
Not supported | Not supported | Supported | |
Disaster recovery and high availability |
|
|
|
Disaster recovery drills | Not supported | Not supported | Supported |
Maximum message retention period | Maximum: 30 days Default: 3 days | Maximum: 30 days Default: 3 days | Maximum: 30 days Default: 3 days You can submit a ticket to customize this setting. After customization, you cannot downgrade the instance to another series. |
Maximum scheduled message delay | Maximum: 7 days | Maximum: 7 days | Maximum: 7 days You can submit a ticket to customize this setting. After customization, you cannot downgrade the instance to another series. |
Non-Serverless series (subscription, pay-as-you-go) instances
Comparison item | Standard Edition | Professional Edition | Platinum Edition |
Product features | Comparable to open source RocketMQ. Provides the following basic features:
| Provides the following enhanced features based on the Standard Edition:
| Provides the following features based on the Professional Edition:
|
Supported | Supported | Supported | |
Disaster recovery and high availability Note Zones are controlled by server-side resource deployment. Custom configurations are not supported. |
|
|
|
Isolation method | Physically shared. Logically single-tenant. | Physically shared. Logically single-tenant. | Physically dedicated. Occupies dedicated physical nodes. |
Stability SLA |
|
|
|
Maximum scheduled message delay | Maximum 7 days | Maximum 40 days | Maximum 40 days |
Instance type limits
All Standard Edition instances and Single Node Edition instances of the Professional Edition do not support burstable elastic computing. You must plan your resource usage in advance to prevent instance throttling when burst traffic exceeds the specification limits during high-watermark runtime.
The topic and group quotas for a single instance are based on practices in large-scale production environments and meet most business requirements. You can split and isolate your business into different instances by department and domain. Avoid running all your business in a single instance.
The TPS specification for message sending and receiving is calculated based on the sum of sent and received normal messages, with a message size of 4 KB as the benchmark. When you calculate the TPS for advanced message types and large messages, you must multiply by the corresponding rate. For more information about the calculation method, see Calculation specifications.
If the actual TPS for message sending and receiving exceeds the upper limit of your purchased instance type:
If the instance has elastic TPS enabled, the instance can run normally within the [Base Specification, Elastic Specification] range. The elastic TPS usage is charged on a pay-as-you-go basis. If the TPS exceeds the upper limit of the elastic capacity, the instance is still throttled.
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 the instance does not support or has not enabled the elastic TPS feature, ApsaraMQ for RocketMQ throttles the instance.
If too many clients connect to an ApsaraMQ for RocketMQ instance, the server uses significant resources to maintain the connections. This can severely affect server stability. Make sure that the number of client connections does not exceed the upper limit for your instance type.
Serverless instances
Number of concurrent online clients: The number of online producer or consumer objects. One producer or one consumer object counts as one client.
Resource count: The total number of topics and consumer groups.
Deployment architecture | Capacity mode | TPS specification | Maximum number of concurrent online clients | Free quota for concurrent online clients | Maximum resource count | Free quota for resource count | Maximum number of LiteTopics that can be created or subscribed to |
Shared | By 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 | 2000 | 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 | 600,000 | ||
15,000 | 8,000 | 6,000 | 6,000 | 500 | 720,000 | ||
[20,000, 50,000] | 10,000 | 8,000 | 6,000 | 500 | 1,000,000 | ||
(50,000, 100,000] | 20,000 | 10,000 | 6,000 | 500 | 1,500,000 | ||
(100,000, 200,000] | 40,000 | 20,000 | 8,000 | 1,000 | 2,400,000 | ||
(200,000, 300,000] | 80,000 | 40,000 | 10,000 | 1,500 | 4,700,000 | ||
(300,000, 500,000] | 100,000 | 50,000 | 16,000 | 2,000 | 6,300,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 types
Instance sub-series | Instance type | Maximum base TPS for message sending and receiving (times/second) | Maximum burst elastic TPS for message sending and receiving (times/second) | Maximum connections | Downstream Internet bandwidth (Mbps) | Free topic quota | Maximum topic quota | Maximum consumer group quota | Maximum number of LiteTopics that can be created or subscribed to |
Single Node Edition (No longer sold) | rmq.s1.micro | 500 | Not applicable This instance type does not support burst elasticity. | 2,000 | 1 to 1000 Customizable. | 100 | 100 | 1,000 | / |
Cluster High-availability Edition | rmq.s2.2xlarge | 2,000 | 4,000 | 300 | 150,000 | ||||
rmq.s2.4xlarge | 4,000 | 4,000 | 250,000 | ||||||
rmq.s2.6xlarge | 6,000 | 6,000 | 500 | 300,000 |
If the highest specification (rmq.s2.6xlarge) of the Standard Edition for topics and consumer groups still cannot meet your business requirements, you can upgrade to the Professional Edition and select a suitable instance type.
Professional Edition instance types
Instance sub-series | Instance type | Maximum base TPS for message sending and receiving (times/second) | Maximum burst elastic TPS for message sending and receiving (times/second) | Maximum connections | Downstream Internet bandwidth (Mbps) | Free topic quota | Maximum topic quota | Maximum consumer group quota | Maximum number of LiteTopics that can be created or subscribed to |
Single Node Edition (No longer sold) | rmq.p1.micro | 500 | Not applicable This instance type does not support burst elasticity. | 2,000 | 1 to 1000 Customizable. | 150 | 150 | 1,500 | / |
Cluster High-availability Edition | rmq.p2.4xlarge | 4,000 | 2,000 | 4,000 | 250,000 | ||||
rmq.p2.6xlarge | 6,000 | 3,000 | 6,000 | 300,000 | |||||
rmq.p2.10xlarge | 10,000 | 5,000 | 10,000 | 1,000 | 600,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 highest specifications (rmq.p2.10xlarge or later) of the Professional Edition for topics and consumer groups still cannot meet your business requirements, you can submit a ticket for assistance.
Platinum Edition instance types
Instance sub-series | Instance type | Maximum base TPS for message sending and receiving (times/second) | Maximum burst elastic TPS for message sending and receiving (times/second) | Maximum connections | Downstream Internet bandwidth (Mbps) | Free topic quota | Maximum topic quota | Maximum consumer group quota | Maximum number of LiteTopics that can be created or subscribed to |
Cluster High-availability Edition | rmq.u2.10xlarge | 10,000 | 5,000 | 10,000 | 1 to 1000 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 of the Platinum Edition still cannot meet your business requirements, you can submit a ticket for assistance.
References
For information about the billable items and billing for subscription and pay-as-you-go instances, see Billing of subscription and pay-as-you-go instances.
For information about the billable items and billing for Serverless instances, see Billing of existing Standard and Professional Serverless instances.