Database Reference
In-Depth Information
There will also be the sagas themselves, such as an instance of
ProcessOrderSaga
and a timeout record while it is saving
ProcessOrderSaga
on IBus.
The timeout and sagas act as messages in the table because we set NHibernate from the
code in the following screenshot in
InitializeNHibernatePersistence.cs
. To
initialize the bus's sagas, timeouts, and subscriptions to NHibernate, this class needs to be
in all the applications. This is because you want the subscriptions of all the applications to
know the subscription definitions in order to transport the messages.
The subscription information that will be saved in SQL Server will be in the
Subscrip-
tion
table to define the queues that are available for the messages to be transported. We
can see that the
ClientBecamePrefered
message will be placed on the
VideoStore.CustomerRelations
queue.
Now, to be clear, the preceding screenshot contains the message subscription's definition
that defines in which queues the messages will be transported to; additionally, since we
have not defined many other variables previously, we know that IBus will use
Da-
faultBuilder()
, XML serialization, and MSMQ transportation by default. If we
want to use SQL Server as our method of transportation, then we will have to use the
