EMS

EMS, or the messaging system, defines system standards for organizations so they can define their enterprise application messaging process with a semantically precise messaging structure. EMS encourages you to define a loosely coupled application architecture in order to define an industry-accepted message structure; this is to ensure that published messages would be persistently consumed by subscribers. Common formats, such as XML or JSON, are used to do this. EMS recommends these messaging protocols: DDS, MSMQ, AMQP, or SOAP web services. Systems designed with EMS are termed Message-Oriented Middleware (MOM).

Let's review the behavior offered by both asynchronous and synchronous communication on the part of applications while messaging.

Note the following about asynchronous communication:

• Both the applications need not be active when they communicate
• No "message received" acknowledgments are required
• Provides nonblocking calls
• Useful when massive communication processing is required
• Allows...