Database Reference
In-Depth Information
Through this table, we know that the timeout for sagas, the saga object itself, the subscrip-
tion information for publish-subscribe, the second-level retries, the fault management, no-
tification, the gateway, and distributor can be supported in MSMQ. Some of these pieces
can be stored in the local memory of the host application; it cannot be saved when the ap-
plication is not running. Pieces can be saved in the RavenDB database, which is a NoSQL
document-oriented database. Pieces can also be saved using the NHibernate database con-
necter, which is an ORM mapper to various relational databases, such as SQL Server,
MySQL, and Oracle. Some of the items have been referred to as data, which is data that
describes the messages versus the messages themselves that will be part of the ESB work-
flow. The workflow itself makes up the business logic, while the messages themselves
could be considered as business objects.
The benefit of NServiceBus is that it will handle the persisting of the object's messages
and various pieces for the developer, as long as the developer has configured NSB cor-
rectly.
For instance, when using NHibernate, NSB will perform the mapping of the messages to
the relational database, and the developer does not have to configure the NHibernate-map-
ping properties to map the objects to the relational database. This saves the developer a lot
of time and effort. The messages themselves can also be persisted through various means
using the settings for using the transport in IBus configurations. These message queues in-
clude MSMQ, Azure queues, SQL Server queues, ActiveMQ, and RabbitMQ.
