- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Developer Guide
- Operation Guide
- Practical Tutorial
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Message APIs
- Cluster APIs
- Namespace APIs
- Topic APIs
- CMQ Message APIs
- CMQ Management APIs
- UnbindCmqDeadLetter
- RewindCmqQueue
- ModifyCmqTopicAttribute
- ModifyCmqSubscriptionAttribute
- ModifyCmqQueueAttribute
- DescribeCmqTopics
- DescribeCmqTopicDetail
- DescribeCmqSubscriptionDetail
- DescribeCmqQueues
- DescribeCmqQueueDetail
- DeleteCmqTopic
- DeleteCmqSubscribe
- DeleteCmqQueue
- CreateCmqTopic
- CreateCmqSubscribe
- CreateCmqQueue
- Other APIs
- Environment Role APIs
- TDMQ for RabbitMQ APIs
- RocketMQ APIs
- DescribeRocketMQVipInstanceDetail
- DescribeRocketMQMsg
- ModifyRocketMQTopic
- ModifyRocketMQNamespace
- ModifyRocketMQGroup
- ModifyRocketMQCluster
- DescribeRocketMQTopics
- DescribeRocketMQNamespaces
- DescribeRocketMQGroups
- DescribeRocketMQClusters
- DescribeRocketMQCluster
- DeleteRocketMQTopic
- DeleteRocketMQGroup
- DeleteRocketMQCluster
- CreateRocketMQTopic
- CreateRocketMQNamespace
- CreateRocketMQGroup
- CreateRocketMQCluster
- TDMQ for RocketMQ APIs
- Production and Consumption APIs
- Data Types
- Error Codes
- SDK Documentation
- FAQs
- TDMQ Policy
- Service Level Agreement
- General References
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Developer Guide
- Operation Guide
- Practical Tutorial
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Message APIs
- Cluster APIs
- Namespace APIs
- Topic APIs
- CMQ Message APIs
- CMQ Management APIs
- UnbindCmqDeadLetter
- RewindCmqQueue
- ModifyCmqTopicAttribute
- ModifyCmqSubscriptionAttribute
- ModifyCmqQueueAttribute
- DescribeCmqTopics
- DescribeCmqTopicDetail
- DescribeCmqSubscriptionDetail
- DescribeCmqQueues
- DescribeCmqQueueDetail
- DeleteCmqTopic
- DeleteCmqSubscribe
- DeleteCmqQueue
- CreateCmqTopic
- CreateCmqSubscribe
- CreateCmqQueue
- Other APIs
- Environment Role APIs
- TDMQ for RabbitMQ APIs
- RocketMQ APIs
- DescribeRocketMQVipInstanceDetail
- DescribeRocketMQMsg
- ModifyRocketMQTopic
- ModifyRocketMQNamespace
- ModifyRocketMQGroup
- ModifyRocketMQCluster
- DescribeRocketMQTopics
- DescribeRocketMQNamespaces
- DescribeRocketMQGroups
- DescribeRocketMQClusters
- DescribeRocketMQCluster
- DeleteRocketMQTopic
- DeleteRocketMQGroup
- DeleteRocketMQCluster
- CreateRocketMQTopic
- CreateRocketMQNamespace
- CreateRocketMQGroup
- CreateRocketMQCluster
- TDMQ for RocketMQ APIs
- Production and Consumption APIs
- Data Types
- Error Codes
- SDK Documentation
- FAQs
- TDMQ Policy
- Service Level Agreement
- General References
- Contact Us
- Glossary
The performance comparison between TDMQ for Apache Pulsar and open-source Apache Pulsar is detailed below:
Item | TDMQ for Apache Pulsar | Apache Pulsar |
Cost | Pay-as-you-go and elastic billing. Cost-effective with no need for dedicated Ops personnel. | Self-built deployments do not support elastic usage, resulting in low resource utilization. Self-built setups require maintenance personnel, leading to higher Ops costs. |
Scalability | It is very flexible and easy to scale. You don't need to pay attention to the scaling process and can fully utilize the scale effect to sustain sudden high loads. | It can add broker nodes flexibly. However, it is complex to manually scale out a BookKeeper cluster, during which maloperations can easily occur and affect the data. |
Availability | It is deployed across multiple AZs, with messages stored in three replicas in different AZs. Tencent Cloud guarantees availability of above 99.95% and supports cluster traffic throttling and optimization to prevent the cluster from being crashed by high traffic. | It requires deployment in different regions to guarantee the availability. You need to ensure the cluster availability in case of a high traffic load on your own. |
Security protection | It natively provides security protection capabilities by using public cloud security products. | It requires the installation of open-source plugins for security protection. |
Monitoring and alarming | It natively provides monitoring and alarming capabilities by using related public cloud products. | It requires the installation of open-source plugins for security protection. |
Summary | Supports pay-as-you-go usage and billing, eliminating the need to manage configurations. Maintenance-free, with no need to handle underlying components. Enables message sending and receiving via cloud API and HTTP protocols, ensuring simplicity and ease of use. Provides high SLA assurance with tailored parameter optimization. | Relies on multiple components, leading to significant Ops efforts. No SLA assurance. Limited security protection capabilities. Difficulty in accurately managing configurations, resulting in resource waste. |
Key Features
1. Message retry and dead-letter mechanism.
2. Tag messages with support for message tag filtering.
3. Added
listenerName identifier on the client side to support multi-network access.4. Optimized server cluster restart latency fluctuations to reduce the impact of restarts on business during fixes or optimizations.
Unique Features
Comprehensive Message Query and Traceability
Supports complete message query and traceability from production, storage, to consumption, enabling users to quickly locate the status of abnormal messages.
Proactive Server Message Redelivery
The server can be configured to proactively redeliver messages that have not been acknowledged for a long time, preventing message loss due to failed acknowledgments. This feature also helps avoid excessive backlog accumulation caused by missed acknowledgments.
Per-Tenant Throttling on a Single Machine
Supports throttling of production and consumption rates and traffic at the tenant level.
Granular Monitoring of Memory Usage, Internal Data Pull Traffic, and Rates for Key Objects
Provides more granular monitoring of critical memory resources, enabling observation and statistics of current memory usage for each resource. Monitoring for message read rates and traffic from bk has also been added.
Visualization of bk Data Compression
Displays comprehensive information about the bk data compression process, including compressed ledgers and the processing time for each ledger.
Throttling and Dynamic Configuration for bk Data Compression Read/Write
Supports read throttling during the compression process to prevent excessive disk bandwidth usage and allows dynamic adjustment of compression throttling capabilities.
Optimized bk Client for Faster Availability Zone Disaster Recovery
Enhances the ability to quickly remove faulty bk nodes, improving the overall cluster recovery speed.
Other Features
Backend Maintenance
The community often does not backport features to older versions. The TDMQ for Apache Pulsar team actively monitors the community, selecting valuable features and bug fixes for integration.
Safeguard and Expert Services
Provides safeguard services for scenarios such as product upgrades, new business launches, and large-scale promotional events, ensuring smooth business operations.
Yes
No
Was this page helpful?