TDMQ for Apache Pulsar
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Pricing Overview
- Pro Cluster
- Getting Started
- Using SDK to Send and Receive Normal Messages
- Developer Guide
- How It Works
- Operation Guide
- Cluster Management
- Monitoring and Alarms
- Permission Management
- Pulsar Instance Permission Management
- Cross-Region Replication
- Practical Tutorial
- API Documentation
- Making API Requests
- Cluster APIs
- Namespace APIs
- CMQ Management APIs
- Environment Role APIs
- TDMQ for RabbitMQ APIs
- RocketMQ APIs
- TDMQ for RocketMQ APIs
- Production and Consumption APIs
- SDK Documentation
- Apache Pulsar TCP Protocol
- General References
Release Notes
Last updated: 2025-04-01 14:26:54
March 2025
Dynamic Name | Dynamic Description | Release Time | Related Documentation |
Support customization of tenant names | Professional cluster, support creating with custom tenant names, user-friendly for migration from self-built to the cloud. | 2025-03-25 | |
Virtual cluster migration to professional cluster | Support virtual cluster migration from professional cluster with a productized interface to get a more functional and stable product form. | 2025-03-25 | |
Producer and consumer usage percentage | Some namespaces will break through the producer and consumer quotas limited by the product, and perform monitoring alarms based on the used quota percentage rather than using a fixed value. | 2025-03-25 |
January 2025
Dynamic Name | Dynamic Description | Release Time | Related Documentation |
Support automatic Topic creation | Professional cluster provides automatic Topic creation, convenient for users to conveniently create metadata. | 2025-01-15 | |
Add default Alarm | For professional cluster, add default alarms for cluster-level TPS, bandwidth, and storage utilization, making it easy for capacity management. | 2025-01-15 | - |
December 2024
Dynamic Name | Dynamic Description | Release Time | Related Documentation |
Professional Cluster, Support Creating Public Network Access Point | Professional clusters provide productized ways to create public network access points. You can also monitor the usage of public network traffic on the cluster monitoring interface. | 2024-12-09 | |
Maximum number of partitions supported is 128. | The professional cluster with "LARGE" cluster specification supports a maximum partition of a single Topic up to 128. | 2024-12-09 |
September 2024
Dynamic Name | Dynamic Description | Release Time | Related Documentation |
Message filtering supports SQL 92 grammar. | Message filtering has added support for more flexible SQL 92 grammar, further enriching the server-side message filtering capacity and simplifying business logic design at the same time. | 2024-09-10 |
August 2024
Dynamic Name | Dynamic Description | Release Time | Related Documentation |
Cross-Region Replication | Professional clusters support replicating messages between cross-region clusters, which can be used for disaster recovery scenarios, data archive, or consumption in a different location. | 2024-08-27 |
March 2024
Dynamic Name | Dynamic Description | Release Time | Related Documentation |
Professional Cluster - Elastic Storage Launched | The professional cluster provides a form of "fixed concurrency scale + elastic storage", ensuring a stable and leading technical architecture, while also reducing storage costs for users. | 2023-3-25 | |
Support external Prometheus integration | Support integrating the monitoring data of professional clusters into self-built Prometheus. While facilitating users' observation, it is possible to adjust the business Workload HPA through monitoring data, making online operation and maintenance more automatic. | 2023-3-25 |
January 2024
Dynamic Name | Dynamic Description | Release Time | Related Documentation |
Professional clusters support cross-region disaster recovery. | Message middleware, as a very important component in the technical architecture of business system, TDMQ Pulsar itself supports disaster recovery capability in multiple availability zones. To address the issue that when a region-level disaster occurs, customers can rapidly migrate their business to ensure business continuity, a Cross-Region Disaster Recovery solution is launched. | 2024-01-11 | |
Cross-regional cold backup solution | Pulsar supports cross-regional cold backup solutions, providing the capability for rapid switching of access points without the need for business transformation. | 2024-01-15 | |
Direct Connect (DC) supports customization of top-level domains. | In the DC scenario, customization of top-level domains is supported, and the cluster can be accessed via the user's own domain name. | 2024-01-20 | - |
Shanghai Autonomous Driving Zone Opened | Pulsar Professional Cluster Shanghai Auto-Driving Zone Opened. | 2024-01-31 | - |
December 2023
Dynamic Name | Dynamic Description | Release Time | Related Documentation |
Professional cluster integrates with TF. | Professional cluster integrates with TF, supporting creation and deletion. | 2023-12-4 | - |
November 2023
Dynamic Name | Dynamic Description | Release Time | Related Documentation |
Pulsar Access Console global resource search | Pulsar Access Console global resource search, convenient for users to quickly locate cluster instances | 2023-11-27 | - |
Open Server in Jakarta | Open Server in Jakarta (Pro Edition) | 2023-11-03 | - |
September 2023
Dynamic Name | Dynamic Description | Release Time | Related Documentation |
Open Zone in Silicon Valley | Professional Edition Open Zone in Silicon Valley | 2023-09-05 | - |
August 2023
Dynamic Name | Dynamic Description | Release Time | Related Documentation |
Topic TTL | Professional clusters support Topic Level TTL, which has a higher priority than namespace and allows for more flexible management of message expiration. | 2023-08-23 |
June 2023
Update | Description | Release Date | Documentation |
Supported creating subscriptions automatically | You can choose whether to enable "Auto-Create Subscription" when creating a namespace. | 2023-06-20 |
May 2023
Update | Description | Release Date | Documentation |
Supported importing roles in batches | You can import roles in batches when managing roles and grant each of them permissions for different namespaces. | 2023-05-29 | - |
June 2022
Update | Description | Release Date | Documentation |
Supported creating non-persistent messages | You can choose to create non-persistent messages in the console and select the number of partitions for such messages. | 2022-06-29 | |
Supported setting limits on cluster quotas | To enhance the stability of virtual clusters, limits are imposed on some cluster quotas. Existing clusters are not affected. The range of the TTL for new namespaces is changed to 60 seconds–1 day. For new virtual clusters, the maximum production/consumption TPS per topic partition is reduced from 50,000 to 5,000, and the maximum production/consumption bandwidth per topic partition is reduced from 50 MB/s to 5 MB/s, so as to avoid the mutual impact between users due to excessive traffic. | 2022-06-29 | |
Supported filtering topics by Type and Creator in the message topic list | - | 2022-06-29 |
December 2021
Update | Description | Release Date | Documentation |
Supported displaying the list of topic producers | You can view the list of topic producers, which helps you locate producer issues more easily. | 2021-12-23 | |
Supported the display of producer/consumer counts and cap alarms | The numbers of producers/consumers and alarms for caps are displayed to promptly notify you of any exceptions in a topic. | 2021-12-23 | |
Supported displaying the number of retries and the acknowledgment status for the message trace feature | The message trace feature allows you to view the subscription modes, the number of retries, and the acknowledgment status of multiple consumers. | 2021-12-23 | |
Supported the pay-as-you-go billing mode | TDMQ for Apache Pulsar supports the pay-as-you-go billing mode and will be billed starting from January 2022. | 2021-12-23 |
October 2021
Update | Description | Release Date | Documentation |
Supported cluster-level data collection | Cluster-level data can be collected, making it easier for you to view the usage details of clusters as a whole. This feature is launched to support the pay-as-you-go billing mode. | 2021-10-27 | |
Supported tag management | Resource tagging and tag authentication with CAM are supported. Resource management is supported for proprietary cloudified businesses. | 2021-10-27 | |
Added topic-level alarms | Topic-level alarms are added for production/consumption speed and traffic and online producer/consumer count. | 2021-10-27 | |
Supported blocking public network access to clusters. You can enable or disable this feature as needed. | - | 2021-10-27 |
August 2021
Update | Description | Release Date | Documentation |
Supported setting the message retention period policy in namespaces | Deletion after consumption: Messages will be cleared within a certain period of time after being acknowledged successfully to save storage space. Persistent retention: No matter whether messages are consumed or not, they will be stored persistently within the maximum retention period and maximum storage space and then deleted chronologically after the limit is reached. | 2021-08-19 | |
Supported forcible deletion of topics and subscriptions | Topic: A topic with subscriptions can be forcibly deleted, along with its subscriptions. Subscription: A subscription can be forcibly deleted even if it has active consumer connections. | 2021-08-19 |
May 2021
Update | Description | Release Date | Documentation |
Launched clusters on v2.7.1 | TDMQ for Apache Pulsar supports clusters on v2.7.1. The cluster version is updated to open-source Pulsar 2.7.1 to support more features and simplify connection. The listenerName dependency is removed for the new cluster version, so you don't need to declare listenerName when connecting to a cluster on v2.7.1 or later from an open-source Pulsar client. | 2021-05-31 |
January 2021
Update | Description | Release Date | Documentation |
Launched the cluster management feature | You can create virtual clusters (which share the underlying resources) and dedicated clusters (which use the underlying resources exclusively) in the console. | 2021-01-14 |
October 2020
Update | Description | Release Date | Documentation |
Launched the message query and message trace features | On the Message Query page, you can query the details and trace of a message, including the message content, parameters, duration of each stage, execution result, producer IP, and consumer IP. | 2020-10-30 | |
Started the open beta test for TDMQ for Apache Pulsar | The open beta test for TDMQ for Apache Pulsar officially starts. No application is required for the trial use. The open beta test has certain limits on the maximum QPS, maximum number of topics, and delayed message concurrency. | 2020-10-12 | - |
September 2020
Update | Description | Release Date | Documentation |
Supported connection to TDMQ for Apache Pulsar from native Pulsar clients | You can connect to TDMQ for Apache Pulsar from native Pulsar clients. For security reasons, you need to configure the appropriate role permissions in the console and configure the token on the client (which works in the same way as JWT token authentication used in the community). | 2020-09-17 | |
Upgraded TDMQ for Apache Pulsar in closed beta test to support the native SDK | TDMQ for Apache Pulsar will be suspended for upgrade between 09:00 AM and 12:00 PM on September 17, 2020 to support connection from native Pulsar clients. | 2020-09-11 | - |
August 2020
Update | Description | Release Date | Documentation |
Launched TDMQ for Apache Pulsar in multiple regions | TDMQ for Apache Pulsar will be available in the Shanghai region starting from August 9, 2020 and in the Beijing and Chengdu regions starting from August 18, 2020. | 2020-08-18 | - |
June 2020
Update | Description | Release Date | Documentation |
Launched TDMQ for Apache Pulsar | TDMQ for Apache Pulsar is a proprietary finance-grade distributed message middleware developed based on Pulsar, a top open-source project of Apache. It features high consistency, reliability, and concurrency. Currently, it is widely used in Tencent's billing scenarios, including core transaction as well as real-time reconciliation, monitoring, and big data analysis. | 2020-06-04 |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No