Pacco VS CAP

I've this project in mind to try it later which looks interesting and covering different topics https://github.com/devmentors/Pacco

With a friend of mine, we've implemented quite some time ago https://github.com/devmentors/Pacco and https://github.com/devmentors/Trill - extremely simple Twitter-like app with additional UI in Blazor https://github.com/devmentors/Trill.Web (similar structure to Pacco, all the infrastructure is running via Docker, and the services can be run locally, via Docker, PM2 or Tye

For Microservices examples, you can check your these guys: https://github.com/devmentors/Pacco

I feel like their packages could reduce the development time of a dotnet microservice by a lot. Here's one of their project showcasing what it can do: https://github.com/devmentors/Pacco

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.