tpcampb
October 19th, 2007, 12:23 PM
Requirements:
Approximately 200 client machines will generate request messages at a rate of 1 message per minute.
Each message should be relatively small… 3-4 k max.
These messages will be sent to a server machine to be processed.
After the message is processed, a response message will be generated and sent back to the client that sent the request.
client will block waiting on a response but will timeout if it waits too long.
Speed and reliability are the most important considerations.
If primary server fails, clients should start communicating with a backup server.
Client machines will be running windows xp, server machines will be running server 2003.
Programs will be written in C# (3.5)
MSMQ sounds like an ideal solution to this scenario. I’ve read several articles about MSMQ and have written simple application.
Can MSMQ handle the load I’ve described efficiently?
How reliable is MSMQ in a business environment?
Would WCF or Remoting be a better choice?
Thanks
Approximately 200 client machines will generate request messages at a rate of 1 message per minute.
Each message should be relatively small… 3-4 k max.
These messages will be sent to a server machine to be processed.
After the message is processed, a response message will be generated and sent back to the client that sent the request.
client will block waiting on a response but will timeout if it waits too long.
Speed and reliability are the most important considerations.
If primary server fails, clients should start communicating with a backup server.
Client machines will be running windows xp, server machines will be running server 2003.
Programs will be written in C# (3.5)
MSMQ sounds like an ideal solution to this scenario. I’ve read several articles about MSMQ and have written simple application.
Can MSMQ handle the load I’ve described efficiently?
How reliable is MSMQ in a business environment?
Would WCF or Remoting be a better choice?
Thanks