- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Developer Guide
- Operation Guide
- Best Practices
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Cluster APIs
- Namespace APIs
- Topic APIs
- Message APIs
- CMQ Message APIs
- CMQ Management APIs
- UnbindCmqDeadLetter
- RewindCmqQueue
- ModifyCmqTopicAttribute
- ModifyCmqSubscriptionAttribute
- ModifyCmqQueueAttribute
- DescribeCmqTopics
- DescribeCmqTopicDetail
- DescribeCmqSubscriptionDetail
- DescribeCmqQueues
- DescribeCmqQueueDetail
- DescribeCmqDeadLetterSourceQueues
- 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
- Best Practices
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Cluster APIs
- Namespace APIs
- Topic APIs
- Message APIs
- CMQ Message APIs
- CMQ Management APIs
- UnbindCmqDeadLetter
- RewindCmqQueue
- ModifyCmqTopicAttribute
- ModifyCmqSubscriptionAttribute
- ModifyCmqQueueAttribute
- DescribeCmqTopics
- DescribeCmqTopicDetail
- DescribeCmqSubscriptionDetail
- DescribeCmqQueues
- DescribeCmqQueueDetail
- DescribeCmqDeadLetterSourceQueues
- 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 Pulsar and open-source Apache Pulsar is detailed below:
Item | TDMQ for Pulsar | Apache Pulsar |
Strengths | It supports on-demand usage and the pay-as-you-go billing mode, eliminating your need to care about configuration. It is Ops-free, eliminating your need to care about the underlying components. It can send/receive messages over the HTTP protocol via TencentCloud API, which is easy to use. It has a high SLA, and its parameters are fine-tuned in a targeted manner. | It stays up to date with new open-source features. It supports flexible parameter configuration |
Shortcomings | It cannot stay up to date with all open-source features in time. | It depends on a large number of components and therefore has a high Ops workload. It doesn't provide an SLA. It has limited security protection capabilities. It cannot be configured precisely, which causes resource waste. |
Cost | It supports on-demand usage and the elastic pay-as-you-go billing mode. It requires no manual Ops, making the cost controllable. | It cannot use resources elastically, resulting in a low resource utilization. It requires manual Ops, incurring high cost. |
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. |
Key Features
1. It supports the message retry and dead letter mechanisms.
2. Tagged messages can be filtered by tag.
3. With the
listenerName identifier added to the client, multi-network access is supported.4. The long restart duration and restart jitters of clusters on the server have been fixed, reducing the impact of restart on your business.
Exclusive Features
All messages and their traces can be queried throughout their lifecycle
TDMQ for Pulsar supports querying messages and their traces throughout the production-storage-consumption lifecycle, which allows you to quickly determine the status of abnormal messages.
The server can actively push messages again
You can configure whether to allow the server to actively push long unacknowledged messages again, which can prevent messages from getting lost due to acknowledgement failures. You will be notified of the acknowledgement failure of messages to avoid the message heap in backlogs.
Throttling can be implemented for a single VM in the tenant dimension
TDMQ for Pulsar supports the throttling of the production/consumption speed and traffic in the tenant dimension.
Refined monitoring metrics are made available for the memory utilization of core resources as well as the internal data pulling speed and traffic
TDMQ for Pulsar provides more refined metrics to monitor the memory utilization of core resources and provides related statistics. It also supports the monitoring of the speed and traffic of reading messages from BookKeeper.
BookKeeper data compression is monitored in a visual manner
TDMQ for Pulsar supports the visual display of the complete BookKeeper data compression information, including the ledger being compressed and the compression duration of each ledger.
Throttling is configured for reads/writes during BookKeeper data compression and can be adjusted dynamically
TDMQ for Pulsar supports read throttling during data compression to avoid excess use of disk and bandwidth. The throttling configuration can be adjusted dynamically.
BookKeeper client is optimized to accelerate disaster recovery in an AZ
TDMQ for Pulsar supports the quick removal of faulty BookKeeper nodes to improve the cluster's overall disaster recovery speed.
Other Features
Backend maintenance
As open-source Pulsar doesn't incorporate some features from previous versions into new releases, TDMQ for Pulsar performs regular backend maintenance by selecting desirable features from the open-source community for further development and bug fixes for enhancements.
Event support and expert service
TDMQ for Pulsar ensures smooth business operations with event support for major events such as product upgrade, new releases, and promotion campaigns.
Yes
No
Was this page helpful?