This topic describes the types and editions of ApsaraMQ for RocketMQ instances and the differences among these instance types and editions. This topic also describes the specifications of each instance edition, including the computing specification, Internet bandwidth, and resource quotas. You can refer to the description in this topic to purchase an instance that meets your business requirements.
Billing methods
Billing method | Description | Scenario | Supported instance edition |
Subscription | You can use an instance only after you pay the computing fees based on the selected computing specification and subscription duration. You are charged for other resources on the instance based on the actual usage. | This billing method is suitable for scenarios in which the amount of traffic is large and stable. |
|
Pay-as-you-go | Computing fees are generated based on the selected computing specification and service duration of an instance after the instance is created. A bill is generated and fees are deducted from your Alibaba Cloud account every hour. You are charged for other resources on the instance based on the actual usage. | This billing method is suitable for test and short-term activity scenarios, such as special marketing activities and end-to-end stress testing activities that require timeliness. If you want to continue using a pay-as-you-go instance after the test or short-term activity is complete, you can change the billing method of the instance to subscription. For more information, see Change the billing method of an instance from pay-as-you-go to subscription. |
|
Serverless | You are charged for resources based on the actual usage. Bills are generated and fees are deducted from your Alibaba Cloud account after the billing cycle (1 hour) ends. | This billing method is suitable for scenarios in which traffic greatly fluctuates or capacity is difficult to evaluate. |
|
Feature differences among instances
Subscription instances and pay-as-you-go instances
Item | Standard Edition instance | Professional Edition | Enterprise Platinum Edition |
Positioning | Developed for entry-level users and provides fully managed messaging services that are fully compatible with Apache RocketMQ. | Developed for enterprise users and provides advanced services that have enterprise-level enhanced features based on Standard Edition instances. | Developed for enterprise VIP customers and provides messaging services that can use exclusive physical resources, custom enhanced features, and expert services based on Professional Edition instances. |
Target users | Suitable for entry-level and cost-sensitive users. | Suitable for users who have a relatively large business scale and high requirements for message availability, stability, and disaster recovery. | Suitable for users who have a large business scale and require custom technical architectures and expert services. |
Capabilities | Provides the following basic capabilities based on Apache RocketMQ:
| Provides the following enhanced capabilities based on Standard Edition instances:
| Provides the following capabilities based on Professional Edition instances:
|
Disaster recovery and high availability (HA) Note The zones in which an instance is deployed are determined by the resources on the ApsaraMQ for RocketMQ broker. You cannot specify custom values for zones. |
|
|
|
Isolation | Instances are logically isolated based on shared physical resources. | Instances are logically isolated based on shared physical resources. | Exclusive instances for each of which a dedicated physical node is provided. |
Stability SLA |
|
|
|
Interval for sending scheduled messages | Maximum value: 7 days. | Maximum value: 40 days. | Maximum value: 40 days. |
Serverless instances
Item | Standard Edition | Professional Edition |
Computing specification | rmq.s3.nxlarge | rmq.p3.nxlarge |
Service availability | 99.95% | 99.95% |
Ratio between transactions per second (TPS) for sending messages and TPS for receiving messages | Adjustment supported | Adjustment supported |
Scalability |
|
|
Interval for sending scheduled messages | Maximum value: 7 days. | Maximum value: 7 days. |
Specification limits
Standard Edition instances and Professional Edition Standalone instances do not support the scaling of computing resources. We recommend that you plan your resource usage to prevent instance throttling caused by traffic that exceeds the specification limit.
The topic and consumer group quotas of an instance are calculated based on actual use cases in large-scale production environments. In most cases, these quotas can meet your business requirements. We recommend that you use different topics and consumer groups for different departments and applications. Do not run all your business in one instance.
Messaging TPS is the total number of times that messages can be sent and received. Messaging TPS is calculated based on a normal message whose size is 4 KB. Multiples must be used when you calculate the TPS for featured messages and large messages. For information about the calculation methods, see Computing specifications.
The following items describe what happens if the actual messaging TPS exceeds the specification limit:
If you enable the elastic TPS feature for an instance and the excess TPS that you use does not exceed the upper limit that is specified by the elastic TPS feature, the instance runs as expected. You are charged for the excess TPS based on a pay-as-you-go basis. If the excess TPS that you use exceeds the upper limit that is specified by the elastic TPS feature, the instance is throttled.
For information about the billing rules of the elastic TPS feature, see Elastic TPS fee.
If the elastic TPS feature is not supported by or enabled for an ApsaraMQ for RocketMQ instance, the instance is throttled.
If a large number of clients are connected to an ApsaraMQ for RocketMQ instance, the broker consumes a large number of resources to maintain the connections. This compromises the stability of the broker. We recommend that the number of connections to an ApsaraMQ for RocketMQ instance does not exceed the specification limit.
Subscription and pay-as-you-go instances
Standard Edition instances
Sub-category edition | Computing specification | Maximum messaging TPS | Maximum elastic TPS | Maximum connections | Outbound Internet bandwidth (Mbit/s) | Maximum topics per instance | Maximum consumer groups per instance |
Standalone Edition | rmq.s1.micro | 500 | N/A Elastic TPS is not supported. | 2,000 | 1 to 1,000 Custom configurations are supported. | 100 | 1,000 |
Cluster High-availability Edition | rmq.s2.2xlarge | 2,000 | 4,000 | 50 | 500 | ||
rmq.s2.4xlarge | 4,000 | 4,000 | 75 | 750 | |||
rmq.s2.6xlarge | 6,000 | 6,000 | 100 | 1,000 |
If the topic and consumer group quotas that are provided by the largest specification (rmq.s2.6xlarge) do not meet your business requirements, we recommend that you upgrade your instance to Professional Edition and select a specification that meets your business requirements.
Professional Edition instances
Sub-category edition | Computing specification | Maximum messaging TPS | Maximum elastic TPS | Maximum connections | Outbound Internet bandwidth (Mbit/s) | Maximum topics per instance | Maximum consumer groups per instance |
Standalone Edition | rmq.p1.micro | 500 | N/A Elastic TPS is not supported. | 2,000 | 1 to 1,000 Custom configurations are supported. | 150 | 1,500 |
Cluster High-availability Edition | rmq.p2.4xlarge | 4,000 | 2,000 | 4,000 | 100 | 1,000 | |
rmq.p2.6xlarge | 6,000 | 3,000 | 6,000 | ||||
rmq.p2.10xlarge | 10,000 | 5,000 | 10,000 | 150 | 1,500 | ||
rmq.p2.20xlarge | 20,000 | 10,000 | 10,000 | ||||
rmq.p2.50xlarge | 50,000 | 20,000 | 14,000 | ||||
rmq.p2.100xlarge | 100,000 | 30,000 | 26,000 | ||||
rmq.p2.150xlarge | 150,000 | 50,000 | 38,000 |
If the topic and consumer group quotas in the largest specification (rmq.p2.10xlarge or above) do not meet your business requirements, submit a ticket.
Enterprise Platinum Edition instances
Sub-category edition | Computing specification | Maximum messaging TPS | Maximum elastic TPS | Maximum connections | Outbound Internet bandwidth (Mbit/s) | Maximum topics per instance | Maximum consumer groups per instance |
Cluster High-availability Edition | rmq.u2.10xlarge | 10,000 | 5,000 | 10,000 | 1 to 1,000 Custom configurations are supported. | 150 | 1,500 |
rmq.u2.20xlarge | 20,000 | 10,000 | 10,000 | ||||
rmq.u2.40xlarge | 40,000 | 20,000 | 10,000 | ||||
rmq.u2.100xlarge | 100,000 | 30,000 | 26,000 | ||||
rmq.u2.150xlarge | 150,000 | 50,000 | 38,000 | ||||
rmq.u2.200xlarge | 200,000 | 60,000 | 50,000 | ||||
rmq.u2.400xlarge | 400,000 | 100,000 | 54,000 | ||||
rmq.u2.600xlarge | 600,000 | 200,000 | 80,000 | ||||
rmq.u2.1000xlarge | 1,000,000 | 300,000 | 134,000 |
If the topic and consumer group quotas in the specifications of Enterprise Platinum Edition instances do not meet your business requirements, submit a ticket.
Serverless instances
Primary instance edition | Computing specification | Peak messaging TPS | Maximum connections | Internet traffic | Maximum topics per instance | Maximum consumer groups per instance |
Standard Edition | rmq.s3.nxlarge | 50,000 | 10,000 | No limit is imposed. You are charged based on your actual usage. | 5,000 | 5,000 |
Professional Edition | rmq.p3.nxlarge | 50,000 If the messaging TPS exceeds 50,000, automatic scaling within minutes is supported. | 30,000 | No limit is imposed. You are charged based on your actual usage. | 5,000 | 5,000 |
References
For information about the billable items and billing rules of subscription and pay-as-you-go instances, see Billable items.
For information about the billable items and billing rules of serverless instances, see Billing of serverless instances.