Best Practices Changes in 7.x

[gokceng]

Hi,
Due to the restrictions my company enforces, I am writing this through mobile with my personal account so there may be some typos.

We are currently migrating from rabbitmq 6.8.1 to 7.1.2. Thanks to migration guides and discussions, we have completed the async/await changes, changing method names, fixing tests etc.

My question will be about the best practices we need to adopt during this migration. For example, in https://www.rabbitmq.com/client-libraries/dotnet-api-guide there are some statements such as Connections are meant to be long-lived. Opening a connection for every operation (e.g. publishing a message) would be very inefficient and is highly discouraged.

Is it possible to see and make a diff of this page (and child pages) compared to 6.x to be able to see if there are any suggestions that are new in 7.x, or if there are any limitations that are removed in 7.x?

I hope it makes sense and I will be happy to elaborate if needed.

Kind regards,
Gokcen

[michaelklishin]

@gokceng you have the same RabbitMQ website git repo as everyone else, and the same git diff as everyone else.

There is a migration document in this repo.

Every recommendation in the guide on connections still applies: connection churn should be avoided or minimized, connections are supposed to be long-lived, and so on.

[gokceng]

I went through all the discussions regarding the migration including the one you shared in the git repo but going through the diff 6.8.1..7.2.1 doesn't make sense, sorry.

What I am asking was if the documentation is version controlled so that I can have a look if any changes made in the documentation. Looking for best practices in the code isn't really logical or realistic.