Database Reference
In-Depth Information
This sample is a video store sample, so we will have:
•
VideoStore.Ecommerce
: The MVC program that starts the bus with the in-
stallations in
Application_Start
given previously. A web page is used to
select orders and the user is given 20 seconds to change their mind with feedback
given to the page through SignalR.
•
VideoStore.Sales
: This has a saga, and handles the timeout and completion
of the orders.
•
VideoStore.Message
: These are common messages for all the endpoints.
•
VideoStore.ContentManagement
: This returns the URL to be selected
after the order is performed.
•
VideoStore.CustomerRelations
: This has the potential to send coupons
to the customers for special offers.
•
VideoStore.Operations
: This has the potential to accept operational mes-
sages such as for errors and reporting at a later time.
This sample works very much like earlier samples discussed for MSMQ, except now all
the pieces are in SQL Server. Or are they?
If we look in MSMQ, it appears empty.
However, if we look in RavenDB for NServiceBus, we notice that tables have been cre-
ated for the various endpoints as normal. They are not populated, but they are created as
place holders for endpoint information.
