NServiceBus vs MassTransit

Question

I\'m struggling with a pros and cons list regarding NServiceBus and MassTransit.

Now I know there is already a thread in here, but it doesn\'t really answer my quest

Answer 1

Just to give a more up to date answer, I've developed professionally with both ecosystems and they both now support a broad range of MQ technologies, and .NET Core.

I used NServicebus a few years back on a new cloud product, we needed .NET Core which Mass Transit didn't support at the time. I have to say - it's a lovely thing to use as developer, there's a lot of nice one liners, great tooling/monitoring and the documentation is really good.

Various levels of support and licence are available, and on the one occasion we needed some help, it was good quality.

---

I've been using Mass Transit for a few months at a new company, and they much prefer having a free, open-source library. The journey has been a bit rockier - the documentation for MT is lacking in places, and a lot of examples/issues are out of date. There's not quite the range of advanced features either, but you may well not need them for their use case.

It works fine though, and the MT developers seem to put a LOT of effort into supporting their OSS - way beyond what you could reasonably expect.

So personally, my TLDR would be - get NServicebus if your company can be convinced to pay for it, but MT is a serviceable alternative and the best you can get for gratis.