TDMQ for Apache Pulsar is a message middleware developed by Tencent based on Apache Pulsar. It provides excellent cloud native and serverless features, is compatible with all components and concepts of Apache Pulsar, and has underlying strengths of compute-storage separation and flexible scaling.
Introduces concepts, advantages and supported regions of TDMQ for Pulsar to help you get started.
This guide introduces the basic concepts, product benefits, billing methods, usage guidelines, and common operations of TDMQ for Apache Pulsar, helping you quickly understand and efficiently use Pulsar.
Overview of product advantages, including high availability, performance, and consistency with the open-source edition.
Compare TDMQ for Apache Pulsar cluster with the open-source edition in terms of compatibility and enterprise-grade enhanced features.
Provides security and compliance guidelines to assist in understanding relevant regulations and ensuring the legal operation of cloud services.
Provides selection guidance for three cluster types: Pro elastic/fixed storage as well as virtual cluster specifications and use cases.
Introduce all billing items involved in the use of TDMQ for Pulsar, including billing methods, billing rules (including special scenarios), and a price overview.
Introduces two billing modes for Pulsar: monthly subscription and pay-as-you-go, and provides pricing details and scenario examples.
Guides users to purchase appropriate cluster specifications via the console based on business requirements.
Explains in detail the calculation methods for cluster and storage costs under the yearly/monthly subscription mode through purchasing and scaling instances in pro clusters.
Introduce how to quickly integrate with the TDMQ for Pulsar
Introduces the CAM permission management mechanism, covering root accounts/sub-accounts, preset and custom policy configurations to enable granular permission control.
Guides you to run send/receive tests using the Java SDK after resource creation, helping you quickly get started with the Pulsar messaging queue service.
Introduces advanced SDK features: load balancing with multiple consumers, retry mechanism, and DLQ (dead letter queue).
Introduce how to configure and use TDMQ for Pulsar, including daily operation and maintenance management, to help you perform hands-on operation.
Introduces the procedures for creating a namespace via the console, including parameter configurations such as naming conventions, message TTL (Time-To-Live), and retention policies.
Introduces methods for creating Topics manually or automatically via the client, including the selection of persistent/non-persistent types and considerations for partition configuration.
Introduces monitoring and alarm capabilities, supporting viewing metrics and configuring alarm rules across multiple dimensions such as cluster, namespace, and Topic levels.
When the cluster specifications cannot meet the requirements, the Pro cluster can be upgraded via the console to adjust the cluster and storage specifications.
Describes migration solutions: dual-read switchover and lossless virtual-to-Pro cluster upgrade practices.
Provides two types of cross-region message replication capabilities—metadata-level and message-level—catering to cross-region disaster recovery and global data archival scenarios respectively.
Learn about practical scenarios of TDMQ for Pulsar to help you use it more efficiently.
Introduces four Pulsar subscription modes: Exclusive, Shared, Failover, and Key_Shared, along with their applicable scenarios.
Supports sending scheduled or delayed messages via APIs, applicable to business scenarios such as order timeout cancellation and task reminders.
Supports message filtering based on exact Tag matching or SQL92 syntax, minimizing ineffective deliveries to reduce bandwidth consumption and improve efficiency.
Introduces automatic retry and proactive retry mechanisms (including negative acknowledgment) after consumption failures, along with the handling approach for dead letter queues.
Analyzes the issue of message gaps caused by discontinuous consumption progress in Shared subscription mode, its causes, and the solution.
When a consumer is blocked due to system failure while the network remains functional, the server can detect the abnormal state, isolate the consumer, and redeliver unacknowledged messages.
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback