Hangfire VS RabbitMQ.NET

Unpopular opinion incoming... What I see is yet another way that the backend JS world is finally achieving something .NET had years ago[0].

Node/Deno/Bun/etc. + npm sounds super straightforward at first glance (and it is at first). But I've thought for years that it's far easier to be productive as an organization on .NET in Visual Studio, since it's simpler to design, deliver, and maintain infrastructure.

[0] https://www.hangfire.io/

you can read about it here HangFire Documentation

I mostly work in .NET, and typically use Hangfire, but all languages has similar frameworks

Its hard to tell what tool would be a best fit without more information, but I would suggest looking at Hangfire for background job processing: https://www.hangfire.io/

You might want to look at https://www.hangfire.io/. Their docs explain how to set up queues: https://docs.hangfire.io/en/latest/background-processing/configuring-queues.html

In this article we looked at how to use Hangfire to schedule background jobs in ASP.NET according to our requirements. In a follow up article, I will talk about using Hangfire with a Redis storage. To learn more about Hangfire, you can visit the official website.

Easy to understand if you want to implement your own background service. If you want a more easy and complete tool you can use hangfire.

Try https://www.hangfire.io/

If, as you stated, you really need to use your own servers, that seems exactly like a job for Hangfire.

In this post, you'll learn how to consume multiple messages on a single channel using the official RabbitMQ.Client for dotnet with the proper caution to avoid concurrency problems or freezing the consumer.