How to access business data in sync with message consumption and modifications to NServiceBus-controlled data.
NServiceBus uses event-driven architecture to include fault-tolerance and scalability in long-term business processes.
NServiceBus gives ACID semantics, using underlying storage so only one worker thread hitting a saga instance can commit.
Correlation is needed in order to find existing saga instances based on data in the incoming message.
Use IFindSaga to write custom code that resolves sagas.
How a message is handled when it could be executed by a saga but no saga could be found.
Call back into a saga after a defined period of time.
How to access business data using connections managed by the NServiceBus NHibernate persistence.
How to control concurrency in sagas with the NHibernate persistence.
Using Azure Storage to store Sagas, Timeouts and Subscriptions.
Using MongoDB to store Sagas and Timeouts.
Using NHibernate to store sagas and timeouts.
Using RavenDB to store Sagas and Timeouts.
How to migrate from one type of saga persistence to another without an off-line migration procedure.
Perform custom saga finding logic based on custom query logic when the Saga storage is a relational database using NHibernate as the ORM.
How build and use a saga.
Perform custom saga finding logic based on custom query logic when the Saga storage is the native SQL Persistence.
Renaming a saga that is stored in the SQL Persistence.
Using SQL Persistence to store sagas and timeouts.