What Is Message-Oriented Middleware?
Message-oriented middleware was designed to decouple the applications or components and allow them to communicate with one another by exchanging messages asynchronously. These messages can be things such as event notifications, application data, request for services, or even objects. Any type of information that needs to be communicated from one application to another is done by passing a message to the receiving system. As you’ll see later in this chapter, various types of messages can be passed from one application to another. Although messages generally can be sent in either direction, certain names are given to the application or component that is sending or receiving a message. The component that creates or produces a message is referred to as a producer. The application or component that receives a message is called a consumer. It’s possible for an application to be both a producer and a consumer of messages, but for a given transfer of information, one side must produce the mess
