Comparison with Apache RocketMQ
Last updated: 2025-07-15 17:42:40
The performance comparison between TDMQ for RocketMQ and Apache RocketMQ is detailed below:
Feature Category | Feature Item | Tencent Cloud TDMQ RocketMQ 5.X | Open-source RocketMQ |
Security Control | Message sending/receiving ACL management | Support fine-grained role refinement for producing and sending messages, with more granular permission refinement. | Default ACL authentication method with single authentication. |
| root account and sub-account | Fully support Tencent Cloud root and sub-accounts, enabling CAM root and sub-accounts, cross-account authorization, and other services within the enterprise. | Not supported |
| Scaling | Customers do not need to care about the size of underlying machines or perform scaling. They only need to purchase appropriate specifications based on business volume and freely adjust specifications as needed. Underlying resources achieve elastic scaling through containerization and automated intelligent ops. | Dependent on a self-built O&M team, with a low level of automation and white-screen issues. |
| High Availability | Tencent Cloud ensures high availability at the underlying cloud level. Customers do not need to worry about deploying disaster recovery architecture. | Self-deployment of a high availability architecture increases operation and maintenance difficulty. |
Migration Tools | Migration Tools | Simultaneously support two migration methods: migrate by importing self-built metadata and changing the access point, and support Seamless Migration with white-screen operation, performing grayscale migration by different Topics in phases. | Migration is not supported. |
Monitoring Alarm | Resource Dashboard | Core metric observation, production and consumption reports, and fine-grained monitoring support drilldown at public network, cluster, topic, group, and topic&group levels; resource Top ranking is provided by cluster granularity. | Simple support, with some monitoring metrics missing. |
| Alarm Management | Message backlog, delay and multiple metric alarms, Cloud Monitor linkage. | Not supported |
elasticity | elastic TPS | Pro Edition and Platinum Version support enabling temporary elastic traffic beyond normal traffic specification. | Not supported. On-demand scaling of machines is required, raising operational complexity. |
| Storage without quota limit | Storage is charged by actual usage. | Not supported. Specified disk size is required at deployment time. Oversized disks may lead to resource waste, and cloud-purchased disks do not support scale-down. Undersized disks require frequent scaling, increasing operation and maintenance difficulty. |
Stability | Distributed throttling | Supports various rate limiting methods and policies (global/local, downgrade policy, multiple rule priorities), effectively avoiding downtime caused by excessively large traffic. | Unsupported. Existence of traffic overload may cause downtime. |
| Message sending and receiving ratio adjustment | Support adjusting the message sending and receiving ratio at the cluster level and perform traffic throttling separately for more reasonable resource utilization. | Not supported |
Message Lifecycle | Topic Level save time setting | Support setting message retention time based on Topic to further save on storage costs. | Not supported |
Console feature optimization | Client stack view | Support, and support code search within the stack. | Not supported |
| Query messages by Tag | Supported | Not supported |
| Query retry/dead letter/delayed message. | Query specific type of messages based on specified conditions. | Not supported |
Compatibility | S3-compatible history for legacy SDK | Fully compatible with ALL legacy SDKs after 4.1. | Not fully compatible, an error occurred in certain scenarios. |
Feature Type | Feature | TDMQ for RocketMQ | Apache RocketMQ |
Basic features | Scheduled message | The scheduled time is accurate down to the second and can be customized. | You can only specify the delay level. |
| Visual management | Visual management for clusters, topics, and groups is supported. You can view the details of subscriptions and consumer status. | Visual management is supported but is less user-friendly. The console doesn’t distinguish between topic types. |
Availability | Elastic scaling | You don’t need to manually deploy, configure, or scale up underlying computing resources because operations such as node registration are automatically performed in a visual manner. You can expand the number of nodes horizontally, increase the disk capacity, and upgrade the configurations of a single node vertically as needed at any time. | A self-built Ops team is required, and operations are performed in a less automatic or visualized manner. |
| High reliability | With three data replicas, the server can be automatically restarted in seconds after the downtime, without affecting the message capacity and data. | Data can be replicated in sync or async mode. You need to design the deployment scheme and related parameters. The primary sync schemes won’t be automatically used after the failover. |
| Cross-AZ high-availability deployment | This feature is supported to avoid losses caused by data center-level failures. | This feature is supported, but it is time-consuming for you to design the deployment schemes and parameters. |
Observability | Resource dashboard | You can monitor core metrics at a fine granularity and view production and consumption details. | This feature is supported but with fewer monitoring metrics. |
| Alarming | With the capabilities provided by Cloud Monitor, alarms will be triggered in case of message heap or delayed message sending/receiving. | Not supported |
Security management and control | Tenant namespace isolation | You can implement this feature in the console in a visual manner. | This feature is not supported. Namespaces cannot be truly isolated due to bugs. |
| Root account and sub-account management | Supports authorization between Tencent Cloud CAM root accounts and sub-accounts and between enterprise accounts. | Not supported |
Migration tool | Tool for migrating from Apache RocketMQ | You can easily migrate from Apache RocketMQ to TDMQ for RocketMQ by using scripts. | - |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback