WCF - MSMQ Architecture suggestion

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.

Tags: WCF, MSMQ