Selection Overview
Before purchasing TDMQ for RabbitMQ, you should consider factors such as performance, peak traffic, cost, and business scenarios to ensure that you select the appropriate cluster specifications for purchase. Cluster forms and specifications, and calculation logics of TDMQ for RabbitMQ exhibit certain differences. This chapter introduces the calculation methods for different cluster versions and specifications to help you make a quick selection.
Product Form Selection
Product Form
TDMQ for RabbitMQ provides two product forms: Managed Edition and Serverless Edition. For details and feature differences, see Capability Comparison. Product Form Selection Recommendations
For Managed Edition and Serverless Edition, you can make a selection based on dimensions such as specification range and applicable scenarios:
|
Managed Edition |
| Number of nodes: 1–7 Number of queues: Up to 1,000 queues per vhost | A clear understanding of the underlying machine resource usage is expected. Fully exclusive cluster resources are required. |
Serverless Edition |
| Cluster TPS specification: 1,000 - 100,000 (with traffic throttling) Number of queues: Up to 6,000 queues per cluster | Traffic peaks (TPS) need to be paid more attention to. Stability issues of open-source RabbitMQ, such as message backlogs and split-brain, have been encountered. Reducing costs is required, including computing and storage costs. There are strong demands for the auto scaling capability. |
Specification Selection
After selecting an edition, you can select the appropriate specifications based on your business usage. The following are the main factors that affect the specification selection:
Serverless Edition is sold based on TPS specifications. For detailed billing instructions, see Serverless Edition. When choosing specifications, you can see the following information: Cluster specifications
Currently, only Pro Edition is available, with TPS specifications ranging from 1,000 to 100,000. For higher specifications, contact us. TPS specification
The peak business traffic needs to be considered. For example, if the peak business traffic is 3,500 TPS, it is required to select at least a specification of 4,000 TPS.
Number of queues
Each TPS specification includes a quota of free queues. If more queues are needed, make additional purchases.
Managed Edition is sold based on node specifications. For detailed billing instructions, see Managed Edition. When choosing specifications, you can see the following information: Node specifications
According to the recommended TPS value per single node in the Product Specifications for Managed Edition, compare the value with your business traffic. The total TPS value for multiple nodes and clusters is not a simple multiple due to factors such as mirrored queues. However, when specifications are selected, it is supported to simply use the product of the number of nodes and the recommended TPS value per node as a reference.
For example, if the long-term business traffic is 6,000 TPS and the recommended TPS value for a 4C16G node is 2400–4000, a 3-node cluster of 4C16G can be purchased.
Number of nodes
Single-node clusters do not guarantee SLA and are recommended only for test environments or verification scenarios.
Multi-node clusters guarantee SLA and can be deployed across multiple AZs to achieve cross-AZ disaster recovery.
Multi-node clusters can enable mirrored queues to ensure high availability.
Single-node storage specifications
Each node requires allocated disk capacity. If larger storage is needed, increase storage specifications during purchase; otherwise, it is recommended to purchase the default minimum storage specifications. Upgrades can be performed later if disk capacity is insufficient.