Capability Comparison
Last updated: 2025-09-04 09:52:25
Tencent Cloud TDMQ for RabbitMQ Serverless Edition is based on an innovative storage-compute separation architecture, fully compatible with the AMQP 0-9-1 protocol and open-source RabbitMQ components and concepts. Through architecture upgrades, it effectively resolves common stability issues in the open-source version, such as split-brain and message backlog, offering advantages like stability, security, and flexible scaling.
TDMQ for RabbitMQ Serverless Edition vs. the original managed open-source series difference comparison as follows:
Architecture and Availability Comparison
Type | Comparison Item | Open-Source Managed | Serverless Version |
Underlying architecture | Open-Source Compatibility | Open-Source Compatibility | Open-Source Compatibility |
| Deployment Architecture | Dedicated Cluster (Exclusive Physical Cluster) | Compute exclusively, storage sharing |
| Storage elasticity | Finite storage space, billed by reserved storage space | No limit on quota, no need to reserve, pay-as-you-go billing |
| Computing elasticity | Add nodes Scale up node specifications | Scale out TPS specifications Follow-up will support automatic elasticity TPS feature |
High Availability | Disaster recovery capability | multi-node support Cross-AZ Deployment disaster recovery Single node does not support Cross-AZ Deployment disaster recovery | Cross-AZ disaster recovery by default |
| Data Persistence | Multi-node supports mirrored queues and replica synchronization | Data persistence with triple replication |
| Service availability SLA | Multi-node ensures service availability: 99.95% Storage reliability: 99.9999999% | Service availability: 99.95% Storage reliability: 99.9999999% |
Feature Comparison
Feature Type | Comparison Item | Open-Source Managed | Serverless Version |
Observability | Monitoring Metrics | 5 dimensions, 50+ monitoring metrics | 4 dimensions, 90+ monitoring metrics |
| Smart inspection | Supports 21 core inspection metrics | Not supported. |
| Prometheus monitoring | Supported. | Not supported. |
Efficient Troubleshooting | Message Query | Supported. | Supported. |
| Message Trace | Not supported | Will be supported, coming soon |
Message and queue related | Delayed Messages | Enable the Delayed Message Plugin to implement | Supported. |
| Arbitration queue | Supported. | Not supported |
| Priority queue | Supported. | Not supported |
Others | Public network access | Supported. | Will be supported, coming soon |
| Access the open-source console | Supported. | Not supported |
Usage Limits Comparison
Restriction Type | Restriction Item | Open-Source Managed | Serverless Version |
Resource usage limits | Number of Vhosts per cluster | 20 | 250 |
| Maximum Connections per Cluster | 10,000 | |
| Maximum number of queues | 1,000 per Vhost limit | 6,000 per cluster limit |
| Maximum switches | 1,000 per Vhost limit | 6,000 per cluster limit |
| Maximum number of channels per connection | 1,024 | 1,024 |
Message Use Limits | Message Size | 128 MB | Pro version: 40 MB, Platinum version will support larger. |
| Maximum delay time for delayed messages | Theoretically unlimited | 30 days |
| Message retention time | Theoretically unlimited | Pro version: 3 days, Platinum version will support larger. |
| Message trace retention time | Message trace not supported | Pro version: 3 days, Platinum version will support larger. |
| Maximum number of message re-entry queue times | Theoretically unlimited | Pro version: 16 times, Platinum version will support larger. |
For more detailed cluster and character usage limits, refer to Open-source Managed Version Usage Limits and Serverless Version Usage Limits.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback