Message Queuing and the Real World

I'm putting together three new sessions for VSLive! in San Francisco. One of these is a session that introduces messaging as an alternative to a more linear approach to network application design. I've implemented MSMQ on a few different applications. One was an accounts payable front end application to an accounting package, and the company that I did it for marveled in the fact that even through their accounting package was down, the accounts payable clerks were still able to work away as if nothing was wrong.

Another application in which I implemented MSMQ was an online commerce application. The web site was up and running for almost a year before the company decided to implement an enterprise back-end accounting system. I decided that regardless of what happened with accounting, people who place orders should be able to enjoy a technobabble-free shopping experience.

As I prepare this session, I was curious if anyone had any interesting implementations of messaging (particularly with MSMQ) in their applications or industries. Any ideas I mention in the session will be accompanied by proper plugs.

Looking forward to hearing new ideas!

3 Comments

  • Hi,

    in my job I use MSMQ to connect loosely coupled data services. Our business is built around collection and distribution of data, we update and distribute to client many GB every day.



    So, we have that infrastructure that consists of data importers, components that write updated data into DB, caching servers, request brokers that know where to look for particular kinds of data etc. Everything is a standalone service that communicates with everything else using common message format pushed through MSMQ. There are some common components - like routers, message multipliers etc - that allow us to redefine the topology of the system on the fly, without changin any code - only configuration of input & output queues for particular component and rules for message routing.



    Works well :)

  • Hey,

    I've build the MSMQ portion of an app recently. Because a legacy system had different availability than the app our team was working on, we used MSMQ to allow our front end app to continue to work regardless of the operational status of the other systems. We used MSMQ Triggers to call a COM+ component that subsequently calls our business tier to perform the work. It works like a charm and the code, although more difficult to debug, the code was relatively easy to write. If the environment we worked in had provided BizTalk, we most likely would have used that, but it didn't and we are getting the desired results from MSMQ.

  • Hello,

    I'm currently using MSMQ for processes that needs long time to execute. I have several duplex web services which get the request (one way), send the process request to windows services (using MSMQ). When the process finish, then the response is sent back to another queue in order to deliver the response to the web service consumer.



    It works very well and we have an high level of scalability.

Comments have been disabled for this content.