Abstractions such as unit of work and message mutators are useful when they perfectly fit what we need to do with them. However, they are abstractions after all, and all nontrivial abstractions, to some degree, are leaky.

What does this mean? If you take a look back at the API for a unit of work, for example, we only get a Begin() and End() method to do any useful work. While this is extremely valuable in some cases, it can also be extremely limiting. Try using it to wrap the message processing in a try/catch or using block, for instance, you will quickly find that the abstraction is fighting against you, not for you.

With NServiceBus 5.0, you get the full power of the new NServiceBus pipeline, giving you the ability to get ridiculously close to the metal and customize nearly every aspect of how NServiceBus sends and receives messages.

The pipeline is new in NServiceBus 5.0 and was originally conceived by the Particular team as a way to simplify and streamline how all...