NServiceBus

What do you like best?

Rich in messaging patterns and abstractions (like pipeline, saga etc.), purely done in .NET, suitable for .NET projects obviously

What do you dislike?

Messaging abstractions are too rich and complex, it's easy to create technical debt if one is not too careful. Sometimes, tools that can do less, but specialize in doing it well, may bring better benefit. I have a feeling similar to when I compare WCF and WebAPI, for example.

Recommendations to others considering the product:

It's a great abstraction of messaging layer, with easy learning curve for .NET developers. If your software includes more messaging patterns than one (e.g. support for e-commerce long running processes, also communication between micro-services etc.) It might be a good option. But if you need just to communicate between services somehow, there might be better alternatives out there, easier to setup and maintain.

What problems are you solving with the product? What benefits have you realized?

Asynchronous communication between microservices, implementing classic long running processes in e-commerce solution (order processing) using NServiceBus sagas