Where I work we have a number of disparate systems, which were all written at different times by different people, luckily all use the same technologies, that being .NET.
Though they are all written in differing versions of .NET, for example my team is lucky enough to be able to work in .NET3.5 SP1 / .NET 4.0, but we must also interface to older systems, and some other newâ€™ish systems.
For the newish systems itâ€™s a no brainer we use WCF, and as we want all messages to be reliable we use MSMQ binding for that.
But for the older systems it is a problem, do you write some custom MSMQ code, or do you look around for some sort of generic messaging solution.
I decided that I would look around and see what was freely available generic messaging solutions are out there, and I decided to write up my findings in a new article which goes into my findings in quite a lot of detail.
The particular framework that I picked up was called NServiceBus which seems to be pretty mature, and has been around for a while and works well with:
- ASP . NET
It also offers Pub/Sub, FullDuplex Client Server types of topology, and inbuilt message persistence using NHibernate, and allows the users to pick their own IOC container of choice.
It seemed to more than fill our requirements. I should mention that it did take me a while to get my head around how NServiceBus does things, all of which I present in the article.
I am really pleased with how the article turned out, and would urge you all to have a read, and if you like what you see please leave me a vote/comment I would appreciate that. These articles do take a while to write/investigate, and it is always nice to know ones hard work is appreciated, so as I say if you like the article please DO leave a vote/comment on the articles forum.
The full article can be obtained here :