Furthermore, the issues identified above compound and multiply. Technically, MQM provides reliable, asynchronous, and loosely coupled communication services. Philosophically, MQM represents the realization by major software vendors of the need for ubiquitous message queue-based communication services. How it Works With MQM, applications communicate with each other as a series of messages. Queues protect messages from being lost in transit and provide a place for receivers to look for messages when they are ready.
Applications make requests by sending messages to queues associated with the intended receiver.
Perhaps most important, messages typically encapsulate requests fully and do not require shared state between sender and receiver. Developers can use MQM providers, along with protocol and message translators, to bridge the gap between dissimilar application architectures. Concurrent execution Journaled communication Connectionless communication. Many applications run only at night, but must receive requests from applications that run only during the day. By sending requests via MQM products, applications are assured that messages will be delivered as soon as network connections become available and receiving applications begin processing.