EasyNetQ VS CAP

For me I’d either go native, or EastNetQ. The latter, while opinionated, is terribly simple to use and has a decent history behind it.

📃What is EasyNetQ? EasyNetQ is designed to make publishing and subscribing with RabbitMQ as easy as possible. of course, you can always use the RabbitMQ client to do this, but it brings lots of complexity of maintenance cumbersome to your application. Digging into this library is out of the scope of this article, you can read more about this incredibly simple library Here.

I recommend trying one of the wrapper libraries as it might be a little easier: https://easynetq.com/

You might want to implement the outbox pattern. There’s a decent library that’ll help and is really easy to integrate. In particular, I’d look at using the transaction functionality

This might be of interest https://cap.dotnetcore.xyz/

There are many libraries in .NET that helps you implementing the outbox pattern like: MassTransit, NServiceBus, CAP. Talking about idempotency, a special mention to a specific lib from a big friend that runs on top of CAP which is called Ziggurat.

CAP is your friend https://github.com/dotnetcore/CAP

Correct but I would actually consider CAP instead. The primary reason is that CAP implements the outbox pattern out-of-box where you would need to implement this yourself with Hangfire.