If you recall, back at the beginning of Chapter 1, Getting on the IBus, I shared several stories of problematic development scenarios, many from my own personal experience. Let's take a look back and reflect on how NServiceBus could prove useful in each situation.

In the first scenario, we were getting deadlocks when updating values in several database tables within a transaction. With NServiceBus, we would separate this action into many different commands, each of which would update the values in one table. By dividing the process, we would create less locking, minimizing the chance of deadlocks in the first place, and automated retry would ensure that the occasional deadlock didn't pose a huge problem. The database would be technically inconsistent for a short period of time until all the commands completed execution, but our business stakeholders would be very happy that end users are no longer getting error messages.

In the second scenario, we were losing orders and...