WCF - MSMQ Architecture suggestion

Question

0.00/5 (No votes)

See more:

Currently, to allow concurrency and load balancing while accessing a resource on server,
An WCF Service is implemented over MSMQ.

Not MSMQBinding, but Just MSMQ.

Client Writes content as Messages on Server's MSMQ queue.
A Windows Service on Server listens to the queue.
Upon receiving a message, it performs the appropriate action using the message content.

This works fine now. Any comments on this architecture?

The only downside seems to be few too many installations

(WCF Service + Win Service) X No.Of Servers

The better alternative seems to be to use netMSMQBinding, so that the WinService can be

replaced by a listener on service host itself.

But, sources say, MSMQ needs to be on client as well as server.

Client -> Client's MSMQ -> Message -> Server's MSMQ -> Server

Is there a way the architecture can skip the Client MSMQ WHILE using netMSMQBinding? Any

pointers?

Note: The solution is deployed on intranet.

Posted 12-Nov-11 18:28pm

Jyothikarthik_N

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

RaisKazi · Accepted Answer · 2011-11-12T18:52:00

WCF can work as a listner to MSMQ messages using netMSMQBinding without any support of any other mechanism like Windows Service etc.

Sometimes it is preferred to keep MSMQ on both Servers Sender and Reciever, Considering in case if Reciever Server is down then you will have your messages in waiting mode in Sender Server's Queue.

In case if you want to avoid MSMQ on Sender's Sever then you can use MessageQueue.ReceiveByCorrelationId Method to make your Remote Message transactions more reliable. Below article has information on this.

http://beaucrawford.net/post/MSMQ-ndash3b-Sending-Messages-to-Remote-Queues.aspx

You may refer below link for more information on MessageQueue.ReceiveByCorrelationId Method.

http://msdn.microsoft.com/en-us/library/4f31cxs4.aspx