Type | Comparison Item | Managed Edition | Serverless Edition |
Underlying architecture | Open-source compatibility | Compatible with open-source RabbitMQ. | Compatible with open-source RabbitMQ. |
| Deployment architecture | Exclusive cluster (exclusive physical cluster). | Exclusive computing resources and shared storage resources. |
| Storage elasticity | Limited storage space. It is billed based on reserved storage space. | Unlimited quota. No reservation is required. It is billed based on usage. |
| Compute elasticity | Horizontally scale out the number of nodes. Vertically scale out the node specifications. | Horizontally scale out the TPS specifications. Automatic elastic TPS will be supported in the future. |
High availability | Disaster recovery capability | Multi-node clusters support cross-AZ disaster recovery deployment. Single-node clusters do not support cross-AZ disaster recovery deployment. | Cross-AZ disaster recovery is supported by default. |
| Data persistence | Multi-node clusters support mirrored queues and multi-replica synchronization. | Data is persisted with a three-replica configuration. |
| Service availability (SLA) | Service availability guaranteed by multi-node clusters: 99.95%. Storage reliability: 99.9999999% | Service availability: 99.95% Storage reliability: 99.9999999% |
Feature Type | Comparison Item | Managed Edition | Serverless Edition |
Observability | Monitoring metric | 5 dimensions and over 50 monitoring metrics. | 4 dimensions and over 90 monitoring metrics. |
| Intelligent inspection | 21 core inspection metrics are supported. | Not supported. |
| Prometheus monitoring | Supported. | Not supported. |
Troubleshooting | Message query | Supported. | Supported. |
| Message trace | Not supported. | Coming soon. Stay tuned. |
Related to messages and queues | Delayed message | It is achieved by enabling the delayed message plugin. | Supported. |
| Quorum queue | Supported. | Not supported. |
| Priority Queue | Supported. | Not supported. |
Others | Public network access | Supported. | Coming soon. Stay tuned. |
| Access to the open-source console | Supported. | Not supported. |
Limit Type | Limit | Managed Edition | Serverless Edition |
Resource use limits | Number of vhosts per cluster | 20 | 250 |
| Maximum number of connections per cluster | 10,000 | |
| Maximum number of queues | Upper limit per vhost: 1,000. | Upper limit per cluster: 6,000. |
| Maximum number of exchanges | Upper limit per vhost: 1,000. | Upper limit per cluster: 6,000. |
| Maximum number of channels per connection | 1,024 | 1,024 |
Message-related limits | Message size | 128 MB | Pro Edition: 40 MB. Platinum Edition will support larger values. |
| Maximum delay time for delayed messages | There is no limit theoretically. | 30 days. |
| Message retention period | There is no limit theoretically. | Pro Edition: 3 days. Platinum Edition will support larger values. |
| Message trace retention period | Message trace is not supported. | Pro Edition: 3 days. Platinum Edition will support larger values. |
| Maximum number of reentry times for messages | There is no limit theoretically. | Pro Edition: 16 times. Platinum Edition will support larger values. |
Feedback