Database Reference
In-Depth Information
Summary
We covered a lot of information in this chapter regarding persistence. This chapter has a lot
of associated code. We covered the highlights of working with NSB and databases. NSB
does take care of a lot of the workings with databases and mappings, but because of the
flexibility of NSB, various pieces can be extended through C# to notify and monitor a vari-
ety of SQL Server pieces.
We covered how to create e-mail notifications by watching queues and notifying operations
of the workings of NSB.
We created a SQL Server database from object code, we created one from EF models, we
created MVC-EF code to read the tables for a PubSub that does most things in SQL Server,
and we changed some of the pieces from EF to NHibernate and then from EF to RavenDB.
We read the subscription tables of NServiceBus in code and displayed them in MVC for
both RavenDB and SQL Server. We also offered a small sample on how to configure a
daily check to send ourselves an e-mail if anything was populated in the MSMQ error
queue. Wow! for a small chapter, the reader has a lot of information to build from.
The next chapter will be more into the code of general persistence. We will discuss
NHibernate, RavenDB, and MongoDB. We will dive into the code to accomplish some
database tasks since it relates to NServiceBus. This code can be applied to many tasks that
are not ESB-specific.
