The Road to Enterprise-Class SOA: Using HTTP and JMS for Web Services
Click here to download now
Overview: In an SOA, a transport needs to be able to convey messages in real time to provide responsiveness to users or systems. The selection of these underlying transports is one of the most important decisions in the creation of an SOA. They must also support different types of synchronous or asynchronous service communication. HTTP and Java Message Service (JMS) are two of the most widely used standards-based transports for SOAP messages. This paper examines the benefits and trade-offs of HTTP and JMS, highlights where each transport is best suited and demonstrates how each can be used as part of SOA.