Database Reference
In-Depth Information
The subscription storage, using NHibernate for the local SQL Express database, will also
be stored in the
nservicebus
database. First, we will install
NSer-
viceBus.NHibernate
via NuGet. This will be the
PubSub-SQL
solution.
You will now have to put the subscription information in the SQL
nservicebus
table.
Even though the subscription table will now be in the SQL database, RavenDB will still
require some of the internal information for NSB, so it must remain running as a service.
In this section, we will be using the
PubSub-SQL
solution:
•
MyMessages
: This is a payment message used for the projects.
•
MyPublisher
: This is a project that publishes
EventMessages
to the SQL
Express
nservicebus
tables for publish or subscribe. The subscription inform-
ation is persisted in the SQL Express
nservicebus
tables instead of RavenDB.
•
Subscriber1
: This is a project for subscribing to the NServicebus
Sub-
scriber1
tables to read and handle
EventMessages
.
•
Subscriber2
: This is a project for subscribing to the NServicebus
Sub-
scriber2
tables to read and handle the
IMyEvent
messages.
This is a publish or subscribe solution to publish messages that
Subscriber1
and
Subscriber2
handle.
Subscriber1
processes one type of messages, whereas
Sub-
scriber2
processes a different type of messages. These were run in VS 2012 in Win-
dows Server 2012, with MSMQ, DTC, NServiceBus references, and SQL Server 2012
Express LocalDB installed. An
nservicebus
database must be present in SQL Server.
