RabbitMQ Best Practices
This section summarizes best practices of Distributed Message Service (DMS) for RabbitMQ in common scenarios. Each practice is given a description and procedure.
Best Practice |
Description |
---|---|
Automatic Recovery of a RabbitMQ Client from Network Exceptions |
This document provides the client reconnection sample code. Clients can be automatically reconnected when network exceptions occur, reducing the impact of network faults on services. |
Automatic Consumer Reconnection After a RabbitMQ Node Restart |
This document provides the consumer reconnection sample code after a RabbitMQ broker restart. A channel can be created for consumers to continue consumption after the previous channel is closed. |
This document describes how to achieve high RabbitMQ performance by setting the queue length, cluster load balancing, priority queues, and other parameters. |
|
This document describes how to improve cluster utilization by configuring queue load balancing among brokers. |
|
This document describes the causes of duplicate messages production and the handling measures. |
|
This document describes security best practices of using RabbitMQ. It aims to provide a standard guide for overall security capabilities. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot