понедельник, 16 мая 2011 г.

NServiceBus Saga Idempotency

Should your business entities had a natural identifier (I think even a surrogate one would do in this case), it would be trivial to ensure idempotency of sagas, that drive their processing.

Just store that Id in a temporal saga storage and enqueue a handler that will guard your sagas as the first handler in NServiceBus endpoint pipe. Something like this one:
And don't forget to specify message handling order:

Good luck!

Комментариев нет: