- 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
What is TDMQ for Apache Pulsar?
TDMQ for Apache Pulsar is Tencent's proprietary messaging middleware based on Apache Pulsar. It comes with excellent cloud native and serverless features and is compatible with all components and principles of Pulsar. It also has the underlying benefits of computing-storage separation and flexible scaling.
TDMQ for Apache Pulsar can add async decoupling and peak shifting capabilities to distributed application systems. It features massive message retention, high throughput, and reliable retry mechanism required by internet applications. Currently, it is widely used in Tencent's most billing scenarios, including primary payment process as well as real-time reconciliation, monitoring, and big data analysis. For more information, see Overview.
How do I use TDMQ for Apache Pulsar?
What are the use cases of TDMQ for Apache Pulsar?
TDMQ for Apache Pulsar can be used in various scenarios such as async decoupling, distributed transaction data consistency, ETL process, and sequential message sending/receiving. For more information, see Use Cases and Practical Tutorial.
What are the strengths of TDMQ for Apache Pulsar over competitors?
TDMQ for Apache Pulsar offers better extensibility and scalability than Kafka and RabbitMQ and has a unique unified message delivery model that covers both the stream and queue features.
TDMQ for Apache Pulsar offers a unified message delivery platform to improve the operations efficiency, reduce system redundancy, and lower the hardware and software costs. For more information, see Strengths.
What Are the Definition and Use Cases of Namespaces in TDMQ for Apache Pulsar?
A namespace is a resource management concept in TDMQ for Apache Pulsar. It allows isolation of different business scenarios and enables specialized configurations for each. Namespaces can also be used to distinguish between production and testing environments.
A Namespace Can Be Used As:
1. The smallest set for adjusting flow control and message storage policies (Topics can only be adjusted in batches by namespace).
2. The smallest set for permission control, where tokens can be configured to have read or write permissions for all Topics under a specific namespace.
Yes
No
Was this page helpful?