Release Notes
Announcements
Parameter | Required | Description |
Cluster Version | Yes | Select 5.x. |
Billing Mode | Yes | Clusters in the 5.x architecture support two modes: pay-as-you-go and yearly/monthly subscription. Monthly subscription: You need to prepay for resources before usage, and the fees are settled based on the order purchase cycle. This mode is suitable for scenarios with steady and long-term usage requirements. Pay-as-you-go: Resources are used first and then paid based on the actual usage duration hourly. This mode is suitable for short-term scenarios such as testing or where traffic peaks are unpredictable. |
Region | Yes | Select the region that is closest to your business. Cloud products located in different regions are completely isolated from each other on the private network, and the region cannot be changed after purchase. Select a region carefully. For example, a Cloud Virtual Machine (CVM) instance in the Guangzhou region cannot access a cluster in the Shanghai region over a private network. If cross-region private network communication is required, see Cloud Connect Network. |
Deployment Mode | Yes | Multi-availability zone (AZ) and single-AZ deployment modes are supported. Single-AZ deployment does not support cross-AZ disaster recovery. It is recommended that you select the multi-AZ deployment mode to enhance the disaster recovery capability. |
Availability Zone | Yes | AZs are physical areas with isolated power and network in the same region. AZs within the same region are interconnected through the private network, and different AZs are physically isolated. Select AZs based on actual requirements. The system can either randomly select AZs or specify AZs. If the multi-AZ deployment mode is selected, two AZs need to be selected for deployment. |
Cluster Specification | Yes | Basic Edition, Pro Edition, and Platinum Edition are supported. Different cluster types vary in performance specifications and features. For details, see Product Series. Basic Edition: It applies to customers with a moderate business scale, and provides fundamental capabilities, including message sending and receiving, compatible with the open-source RocketMQ. Pro Edition: It applies to enterprise-level customers with a large business scale but no special requirements for physical resource isolation, and supports underlying resource sharing, up to 100,000 TPS, and enhanced features, including elastic TPS. Platinum Edition: It applies to large enterprise customers with physical isolation requirements and large-scale business scenarios. It is the only specification type with exclusive underlying resources, supports up to million-level TPS, and provides more features and professional support services from technical experts. |
TPS Specification | Yes | The TPS specification includes the sum of production messages and consumption messages. Each message is calculated in units of 4 KB. Special types of messages are calculated based on a specific ratio. For details, see Billing Overview. Basic Edition: 1,000–10,000 TPS Pro Edition: 4,000–100,000 TPS Platinum Edition: 10,000–1,000,000 TPS You can select the appropriate TPS specifications based on business traffic requirements. Subsequent configuration changes can be made quickly in the console. For specific operations, see Adjusting Cluster Specifications. |
Message Retention Period | Yes | Messages are retained for 3 days by default. After the message retention time expires, messages are deleted regardless of whether the messages are consumed. For clusters of Basic Edition, the message retention time can be adjusted to 1 to 3 days at the cluster level. For clusters of the Pro/Platinum edition, the message retention time can be adjusted to 1 to 7 days at the topic level. |
Topic Count | Yes | Each cluster specification provides a certain number of topics for free. Additional topics require extra fees. For details, see Billing Overview. |
Number of Groups | Yes | The default ratio of the number of topics to the number of groups is 1:10. The group quota is free of charge. You can adjust it by adjusting the number of topics. |
VPC | Yes | Authorize binding the access point domain name of the newly purchased cluster to Virtual Private Cloud (VPC). |
Public Network Access | No | Enabling public network bandwidth will incur additional fees. You can disable it on the Cluster Management page after activation. For details, see Configuring Public Network Access. |
Cluster Name | Yes | Enter a cluster name that complies with the naming rules: The name must be 3 to 64 characters in length and can contain only digits, letters, hyphens (-), and underscores (_). |
Tag | No | Tags are used to classify and manage resources from different dimensions. For specific usage, see Configuring Resource Tags. |
Terms of Service | Yes | Select I have read and agree to the TDMQ for RocketMQ Terms of Service. |
Parameter | Required | Description |
Cluster Version | Yes | Select 4.x. |
Cluster Type | Yes | Exclusive clusters: Exclusive physical resources, high data security, and virtually unrestricted usage. You can purchase on demand according to different node specifications. General clusters: Exclusive physical resources, high data security, and virtually unrestricted usage. Sold based on TPS ranges with fixed node specifications. |
Billing Mode | Yes | Only the yearly/monthly subscription (prepaid) billing mode is supported. |
Cloud Migration Components | No | If you need to migrate self-built clusters to the cloud, a migration component needs to be installed separately to adapt to clusters migrated to the cloud. You can enable the Cloud Migration Component switch when purchasing a 4.x exclusive cluster. After it is enabled, a migration component is installed separately to support seamless migration of self-built clusters to the cloud. TDMQ for RocketMQ 4.x general clusters and 5.x series clusters are not affected by the migration component. You can directly use the purchased cluster. |
Region | Yes | Select the region that is closest to your business. Cloud products located in different regions are completely isolated from each other on the private network, and the region cannot be changed after purchase. Select a region carefully. For example, a CVM instance in the Guangzhou region cannot access a cluster in the Shanghai region over a private network. If cross-region private network communication is required, see Cloud Connect Network. |
Deployment Mode | Yes | Multi-AZ and single-AZ deployment modes are supported. Single-AZ deployment does not support cross-AZ disaster recovery. It is recommended that you select the multi-AZ deployment mode to enhance the disaster recovery capability. |
Availability Zone | Yes | AZs are physical areas with isolated power and network in the same region. AZs within the same region are interconnected through the private network, and different AZs are physically isolated. Select AZs based on actual requirements. The system can either randomly select AZs or specify AZs. If the multi-AZ deployment mode is selected, two AZs need to be selected for deployment. |
Cluster Specification | Yes | Select an appropriate cluster specification based on business requirements. Exclusive clusters are sold based on different node specifications, and general clusters are sold based on TPS ranges with fixed node specifications. You can quickly adjust the configuration in the console later. For specific operations, see Adjusting Cluster Specifications. |
Topic Count | Yes | Each cluster specification provides a certain number of topics for free. Additional topics require extra fees. For details, see Billing Overview. |
Number of Groups | Yes | The default ratio of the number of topics to the number of groups is 1:10. The group quota is free of charge. You can adjust it by adjusting the number of topics. |
VPC | Yes | Authorize binding the access point domain name of the newly purchased cluster to VPC. |
Public Network Access | No | Enabling public network bandwidth will incur additional fees. You can disable it on the Cluster Management page after activation. For details, see Configuring Public Network Access. |
Cluster Name | Yes | Enter a cluster name that complies with the naming rules: The name must be 3 to 64 characters in length and can contain only digits, letters, hyphens (-), and underscores (_). |
Tag | No | Tags are used to classify and manage resources from different dimensions. For specific usage, see Configuring Resource Tags. |
Terms of Service | Yes | Select I have read and agree to the TDMQ for RocketMQ Terms of Service. |
フィードバック