Best Practices for Managing RabbitMQ Channels in .NET Core 8

[ayalaSuperUser]

Hi everyone,

I’m working with RabbitMQ.Client 6.4.0 in a .NET Core 8 application and looking for best practices regarding connection and channel management in a multithreaded environment.

Current Implementation:

We use a single TCP connection (injected as a singleton).
Messages are processed in parallel using Task.Run, where each message is handled asynchronously like this:

await (Task)concreteType.GetMethod("Handle").Invoke(handler, new object[] { @event });

Plan & Questions:

I plan to upgrade to RabbitMQ client 7 in the near future, so I have not yet separated the connection into two different connections as currently recommended.

I am considering modifying the infrastructure to support multiple channels and need guidance on the best approach. Specifically:

1. Should I create a new channel per scope/transient?
   This would mean generating a new channel for each request.
2. Are there any best practices for managing channels efficiently while ensuring performance and reliability?

I’ve created a GitHub repository with a minimal example showcasing my current implementation: rabbitmq-netcore-wrapper

I’d greatly appreciate any feedback or suggestions on improving my approach!

Thanks in advance!

Best,
Ayala

[lukebakken]

Hello, when I have time I'll review your code.

Just FYI, version 7 of this client is the latest and is the version you should be targeting.

[ayalaSuperUser]

Thanks for your assistance.
You're right about the RabbitMQ client version—I’ve updated it accordingly.
Ayala.

[lukebakken]

Please, do NOT contact me directly. I will try to make time to review your code.

I am usually busy helping people or companies who PAY for RabbitMQ support.

[ayalaSuperUser]

I sincerely apologize for my mistake. I misunderstood the group's rules, and I didn’t intend to cause any issues.

[lukebakken]

misunderstood the group's rules

It's generally understood that to contact someone directly about the free software they maintain is very rude. It's not just "the group's rules".

[lukebakken]

@ayalaSuperUser - let's continue discussion in your repository. I opened this issue recently - ayalaSuperUser/rabbitmq-netcore-wrapper#1