This means the sender application doesn't have to wait until the receiver application receives the message. The sender application is free to send a message and continue doing other work
In a decentralized architecture, there is no message server. Tasks such as persistence, transaction, and security are taken care of by the client systems. Thus, the client systems are capable of performing the enterprise services on the messages. Message routing, that is, the sending of messages to their proper destinations, is delegated to the network router
ted to support the messaging system and not the Remote Procedure Call (RPC) based systems, such as those using CORBA and Enterprise JavaBeans (EJB) architecture
The publish-and-subscribe or pub/sub model is intended for broadcasting one-to-many messages, and the point-to-point queuing or p2p method is intended for broadcasting one-to-one messages
However, in JMS, an option exists that allows P2P clients to use a push model that is similar to the pub/sub model. A queue may have multiple receivers, but only one receiver may consume each message at a time.