Recently, I stumbled upon an interesting problem related to NServiceBus Saga concurrency and coarse-grained locks when using NHibernate Persistence.
With NServiceBus,Ā concurrent access to an existing saga instanceĀ works out of the box. This is because it relies on the underlying database system. WithĀ NHibernate, it relies on optimistic concurrency, by adding a Version column to your Saga Data. But there is a catch: NHibernate doesn’t support Coarse-Grained Locks. Let’s first explore this general problem and then we’ll get back to the NServiceBus Saga.
Coarse-Grained Locks
With a coarse-grained lock you basically lock a group of entities together. If you’re familiar with DDD, then you know that an aggregate should be a consistency boundary. When I save an aggregate, I want to save theĀ entireĀ aggregate, to ensureĀ it’s consistent. Why would you need this? Here’sĀ an example:
Let’s take the already familiar example of an Order with OrderLines, Order being the aggregate root. We’reĀ using optimistic concurrency control for each of our aggregate parts.Ā In our domain there isĀ an invariant that dictates that the total number of items Ā in an order can’t be more than 10. Two commands that would increase the quantity could be processed in parallel and break the invariant. This is because in each transaction, the invariant would hold and each transaction would commit, since theyĀ update differentĀ lines. Now you’re in an inconsistent state.
If we could lock the entire aggregate (order and order lines), then the second transaction would fail andĀ rollback, maintaining a consistent state. One way to achieve this when using optimistic concurrency is to update the root’s version whenever an aggregate part is updated.
Continue Reading
