What is the best practice?

[l-7-l]

Sorry, this may be an irrelevant question. I am new to service programming. Recently, I am building a monolithic service and using rabbitmq for decoupling. I don’t know how to use amqprs in a production environment. What is the best practice. How to deal with concurrency? When should a new channel be opened? Is there any project/example recommended for production environment?

[gftea]

Hi,

RabbitMQ has a good documentation https://www.rabbitmq.com/, read there for more practical advices
In general, do not use more resource than you need,

1. Channel multiplexed on a connection, do not use more channels than you need because it increase multiplexing, demultiplexing costs and data usage
2. do not use more queues than you need, because it increase routing costs also in the server

[michaelklishin]

Some guides I wish every new user would read early in their journey with RabbitMQ:

• Production Checklist
• Connections
• Channels
• Runtime (you don't have to tune anything in the beginning but at least be aware of what is covered in that guide)
• Queues
• Quorum queues (classic mirrored queues are deprecated and will be removed in RabbitMQ 4.0)
• Streams and superstreams (there is a separate Rust client for these)