Usage Considerations MOM is most appropriate for event-driven applications . When an event occurs, the client application hands off to the messaging middleware application the responsibility of notifying a server that some action needs to be taken. Asynchronous and synchronous mechanisms each have strengths and weaknesses that should be considered when designing any specific application. As such, a negative aspect of MOM is that a client process can continue to transfer data to a server that is not keeping pace. Many MOM implementations currently exist that support a variety of protocols and operating systems.
Many implementations support multiple protocols and operating systems simultaneously.
Some vendors provide tool sets to help extend existing interprocess communication across a heterogeneous network. Costs and Limitations MOM is typically implemented as a proprietary product, which means MOM implementations are nominally incompatible with other MOM implementations. Using a single implementation of a MOM in a system will most likely result in a dependence on the MOM vendor for maintenance support and future enhancements. This could have a highly negative impact on a system's flexibility, maintainability, portability, and interoperability. The flexibility to choose a MOM implementation may be dependent on the chosen application platform or network protocols supported, or vice versa.