The difference between MQ and WebService, the difference between MQ

Webservice and MQ (MessageQueue) are common means of solving cross-platform communication, what are the differences between them?

personally, the most essential difference is that webservice near real-time communication, while MQ is usually delayed communication. What do you mean? Because WebService is actually the local server program calls the method on the remote server, the interaction between the two, the request needs to wait for the requested server to respond, the other end will be the action, that is, if you request the service server shut down, or interrupted, Then you certainly will not have the answer, your request even if it is lost. And MQ is the equivalent of a middleware I send a request must first be communicated to the Message Queuing component, and then by the Message Queuing component to another server to request, have a response and then return to the original requestor, because the MessageQueue component will persist the message on the local, So even if the sudden crash, the request message is not lost. For example, we have a complex request to generate a report, to generate a report can be quite complicated, so for a few minutes, then we certainly can not wait there, this time using MQ, according to the request report to the requirements of MQ, wait until the receiver processing return, I will receive notification, so it is better. Common MQ components include MSMQ, Apache ACTIVEMQ, and some open source MQ. What is MQ's role in shaving and decoupling?

The difference between MQ and WebService, the difference between MQ