A category of software infrastructure focused on the sending and receiving of messages between distributed systems. It acts as an intermediary layer that allows independent software components to communicate without being directly connected, regardless of their physical location or programming languages.
At its core, MOM provides a store-and-forward mechanism. When an application sends data, the middleware accepts it, stores it in a reliable buffer (such as a queue), and delivers it to the recipient when the recipient is ready to process it.
MOM Principles
- Asynchronous Communication: The sender (producer) does not need to wait for the receiver (consumer) to respond. It can fire and forget, continuing its own operations immediately.
- Decoupling: Systems do not need to know each other’s network addresses or internal states. They only need to know the name of the destination (queue or topic) hosted by the MOM.
- Reliability & Persistence: Most MOM implementations ensure that messages are not lost if a network goes down or a server crashes. The middleware stores the message on disk until delivery is confirmed.
- Time Independence: The sender and receiver do not need to be online at the same time. The MOM holds the message until the receiver reconnects.
Common Messaging Patterns
MOM typically facilitates two primary ways of moving data:
- Point-to-Point (PTP): A message is sent to a specific Queue. Only one consumer will receive and process that specific message. Once processed, the message is removed from the queue.
- Publish/Subscribe (Pub/Sub): A message is published to a Topic. Multiple subscribers interested in that topic will each receive a copy of the message. This is ideal for broadcasting information to many systems simultaneously.
MOM Components
| Component | Role |
| Producer/Sender | The application that creates the data and sends it to the middleware. |
| Message Broker | The central server or cluster that routes, stores, and manages the messages. |
| Destination | A logical address (Queue or Topic) where messages are stored. |
| Consumer/Receiver | The application that retrieves and processes the message from the destination. |
Why Use MOM?
In modern enterprise architecture, MOM is used to handle bursty traffic and fault tolerance. For example, in a retail system:
- The Web Store sends an Order Placed message to the MOM.
- The Inventory System and Shipping System both listen for that message.
- If the Shipping System is undergoing maintenance, the message sits safely in the MOM. As soon as the system comes back online, it picks up the orders exactly where it left off, ensuring no data is lost.
Additional Acronyms for MOM
- MoM - Month over Month