Why not using sockets instead of MSMQ while Microsoft uses MSMQ for the Commerce portal?
Hi Ramon, MSMQ is more than just a form of communication. It provides end to end reliable messaging between applications. For example, MSMQ provides: Transaction Processing - Gauranteed delivery. All or nothing processing. Asynchronous communication - Other side can be offline, messages wait till other side is back online. Routing and Priority - Efficient routing if there are many hops to traverse. Messages are kept secure along the way. Routing, security etc is automatic, no need for application to worry about it, except to set a few flags every now and then. In terms of Commerce Portal, it uses something called asynchronous communication. That means, if one of the servers goes down, eg the database is rebooted, the messages or transactions are not lost, but are instead queued waiting for the database to return. So for example, imagine that you are a shopper on a Commerce Portal online market. You fill your basket and go to the checkout. Just before you click on send, an administrator decides to reboot the navision server. If a reliable messaging system were not in place, you would probably get some sort of error message, or even worse, it will process the order but not log it in the database. With MSMQ, the shopper can submit orders and browse items even if the navision database is down, but any transactions that he makes will be processed when navision is back up again. Microsoft probably explains this better: http://www.microsoft.com/windows2000/technologies/communications/msmq/default.asp Regards, Edd.
Very good info, thx
thx Edward… This is making it more clear