Release Notes and Announcements

Release Notes

Announcements

Product Introduction

Introduction and Selection of the TDMQ Product Series

What Is TDMQ for RabbitMQ

Strengths

Use Cases

Description of Differences Between Managed Edition and Serverless Edition

Open-Source Version Support Description

Comparison with Open-Source RabbitMQ

High Availability

Use Limits

TDMQ for RabbitMQ-Related Concepts

Regions

Related Cloud Services

Billing

Billing Overview

Pricing

Billing Example

Convert to Monthly Subscription from Hourly Postpaid

Renewal

Viewing Consumption Details

Overdue Payments

Refund

Getting Started

Getting Started Guide

Step 1: Preparations

Step 2: Creating a RabbitMQ Cluster

Step 3: Configuring a Vhost

Step 4: Using the SDK to Send and Receive Messages

Step 5: Querying a Message

Step 6: Deleting Resources

User Guide

Usage Process Guide

Configuring the Account Permission

Creating a Cluster

Configuring a Vhost

Connecting to the Cluster

Managing Messages

Configure Advanced Feature

Managing the Cluster

Viewing Monitoring Data and Configuring Alarm Policy

Use Cases

Use Instructions of Use Cases

RabbitMQ Client Use Cases

RabbitMQ Message Reliability Use Cases

Usage Instructions for MQTT Protocol Supported by RabbitMQ

Migrate Cluster

Migrating RabbitMQ to Cloud

Step 1. Purchasing a TDMQ Instance

Step 2: Migrating Metadata to the Cloud

Step 3: Enabling Dual Read-Write

API Reference (Managed Edition)

API Overview

API Reference (Serverless Edition)

History

Introduction

API Category

Making API Requests

Relevant APIs for RabbitMQ Serverless PAAS Capacity

RabbitMQ Serverless Instance Management APIs

Data Types

Error Codes

SDK Documentation

SDK Overview

Spring Boot Starter Integration

Spring Cloud Stream Integration

Java SDK

Go SDK

Python SDK

PHP SDK

Security and Compliance

Permission Management

Network Security

Deletion Protection

Change Records

CloudAudit

FAQs

Service Level Agreement

Capability Comparison

PDF

Mode fokus

Ukuran font

Terakhir diperbarui: 2026-01-04 14:53:46

TDMQ for RabbitMQ Serverless Edition of Tencent Cloud adopts an innovative storage-compute separation architecture, and it is fully compatible with the AMQP 0-9-1 protocol and all components and concepts of open-source RabbitMQ. Through architecture upgrades, it effectively addresses common stability issues seen in the open-source version, such as split-brain and message backlogs. Serverless Edition provides strengths, such as stability, security, and flexible scaling.
After comparison, the detailed differences between TDMQ for RabbitMQ Serverless Edition and the original Managed Edition series are as follows:
Architecture and Availability Comparison
Type
Comparison Item
Managed Edition
Serverless Edition
Underlying architecture
Open-source compatibility
Compatible with open-source RabbitMQ.
Compatible with open-source RabbitMQ.
﻿
Deployment architecture
Exclusive cluster (exclusive physical cluster).
Exclusive computing resources and shared storage resources.
﻿
Storage elasticity
Limited storage space. It is billed based on reserved storage space.
Unlimited quota. No reservation is required. It is billed based on usage.
﻿
Compute elasticity
Horizontally scale out the number of nodes.
Vertically scale out the node specifications.
Horizontally scale out the TPS specifications.
Automatic elastic TPS will be supported in the future.
High availability
Disaster recovery capability
Multi-node clusters support cross-AZ disaster recovery deployment.
Single-node clusters do not support cross-AZ disaster recovery deployment.
Cross-AZ disaster recovery is supported by default.
﻿
Data persistence
Multi-node clusters support mirrored queues and multi-replica synchronization.
Data is persisted with a three-replica configuration.
﻿
Service availability (SLA)
Service availability guaranteed by multi-node clusters: 99.95%.
Storage reliability: 99.9999999%
Service availability: 99.95%
Storage reliability: 99.9999999%
Feature Comparison
Feature Type
Comparison Item
Managed Edition
Serverless Edition
Observability
Monitoring metric
5 dimensions and over 50 monitoring metrics.
4 dimensions and over 90 monitoring metrics.
﻿
Intelligent inspection
21 core inspection metrics are supported.
Not supported.
﻿
Prometheus monitoring
Supported.
Not supported.
Troubleshooting
Message query
Supported.
Supported.
﻿
Message trace
Not supported.
Coming soon. Stay tuned.
Related to messages and queues
Delayed message
It is achieved by enabling the delayed message plugin.
Supported.
﻿
Quorum queue
Supported.
Not supported.
﻿
Priority Queue
Supported.
Not supported.
Others
Public network access
Supported.
Coming soon. Stay tuned.
﻿
Access to the open-source console
Supported.
Not supported.
Use Limit Comparison
Limit Type
Limit
Managed Edition
Serverless Edition
Resource use limits
Number of vhosts per cluster
20
250
﻿
Maximum number of connections per cluster
There are recommended values. For details, see Product Specifications.
10,000
﻿
Maximum number of queues
Upper limit per vhost: 1,000.
Upper limit per cluster: 6,000.
﻿
Maximum number of exchanges
Upper limit per vhost: 1,000.
Upper limit per cluster: 6,000.
﻿
Maximum number of channels per connection
1,024
1,024
Message-related limits
Message size
128 MB
Pro Edition: 40 MB. Platinum Edition will support larger values.
﻿
Maximum delay time for delayed messages
There is no limit theoretically.
30 days.
﻿
Message retention period
There is no limit theoretically.
Pro Edition: 3 days. Platinum Edition will support larger values.
﻿
Message trace retention period
Message trace is not supported.
Pro Edition: 3 days. Platinum Edition will support larger values.
﻿
Maximum number of reentry times for messages
There is no limit theoretically.
Pro Edition: 16 times. Platinum Edition will support larger values.
For more detailed use limits on the clusters and characters, see Use Limits of Managed Edition and Use Limits of Serverless Edition.

Bantuan dan Dukungan

Apakah halaman ini membantu?

Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.

masukan

Type	Comparison Item	Managed Edition	Serverless Edition
Underlying architecture	Open-source compatibility	Compatible with open-source RabbitMQ.	Compatible with open-source RabbitMQ.
		Deployment architecture	Exclusive cluster (exclusive physical cluster).	Exclusive computing resources and shared storage resources.
		Storage elasticity	Limited storage space. It is billed based on reserved storage space.	Unlimited quota. No reservation is required. It is billed based on usage.
		Compute elasticity	Horizontally scale out the number of nodes. Vertically scale out the node specifications.	Horizontally scale out the TPS specifications. Automatic elastic TPS will be supported in the future.
High availability	Disaster recovery capability	Multi-node clusters support cross-AZ disaster recovery deployment. Single-node clusters do not support cross-AZ disaster recovery deployment.	Cross-AZ disaster recovery is supported by default.
		Data persistence	Multi-node clusters support mirrored queues and multi-replica synchronization.	Data is persisted with a three-replica configuration.
		Service availability (SLA)	Service availability guaranteed by multi-node clusters: 99.95%. Storage reliability: 99.9999999%	Service availability: 99.95% Storage reliability: 99.9999999%

Feature Type	Comparison Item	Managed Edition	Serverless Edition
Observability	Monitoring metric	5 dimensions and over 50 monitoring metrics.	4 dimensions and over 90 monitoring metrics.
		Intelligent inspection	21 core inspection metrics are supported.	Not supported.
		Prometheus monitoring	Supported.	Not supported.
Troubleshooting	Message query	Supported.	Supported.
Troubleshooting		Message trace	Not supported.	Coming soon. Stay tuned.
Related to messages and queues	Delayed message	It is achieved by enabling the delayed message plugin.	Supported.
		Quorum queue	Supported.	Not supported.
		Priority Queue	Supported.	Not supported.
Others	Public network access	Supported.	Coming soon. Stay tuned.
Others		Access to the open-source console	Supported.	Not supported.

Limit Type	Limit	Managed Edition	Serverless Edition
Resource use limits	Number of vhosts per cluster	20	250
		Maximum number of connections per cluster	There are recommended values. For details, see Product Specifications.	10,000
		Maximum number of queues	Upper limit per vhost: 1,000.	Upper limit per cluster: 6,000.
		Maximum number of exchanges	Upper limit per vhost: 1,000.	Upper limit per cluster: 6,000.
		Maximum number of channels per connection	1,024	1,024
Message-related limits	Message size	128 MB	Pro Edition: 40 MB. Platinum Edition will support larger values.
		Maximum delay time for delayed messages	There is no limit theoretically.	30 days.
		Message retention period	There is no limit theoretically.	Pro Edition: 3 days. Platinum Edition will support larger values.
		Message trace retention period	Message trace is not supported.	Pro Edition: 3 days. Platinum Edition will support larger values.
		Maximum number of reentry times for messages	There is no limit theoretically.	Pro Edition: 16 times. Platinum Edition will support larger values.

tencent cloud

TDMQ for RabbitMQ

Capability Comparison

Architecture and Availability Comparison

Feature Comparison

Use Limit Comparison

Bantuan dan Dukungan