Oracle Service Bus accommodates multiple messaging paradigms and supports the following TYPES of communication:

• Synchronous request/response
• Asynchronous publish one-one
• Asynchronous publish one-many
• Asynchronous request/response (synchronous-to-asynchronous BRIDGING).

In sync-async bridging, a synchronous client issues a request to an asynchronous provider. For this pattern, Oracle Service Bus provides the capability to publish a message on one JMS queue and configure a second JMS queue for the response, with a timeout value for LISTENING for the response. This type of service appears as a synchronous service to the service CONSUMER. Using asynchronous request/response messages has these advantages: 

• No blocking by the request thread, removing thread management issues that can occur when NUMEROUS blocking request/response invocations are made.
• More reliable messaging

Oracle Service Bus accommodates multiple messaging paradigms and supports the following types of communication:

In sync-async bridging, a synchronous client issues a request to an asynchronous provider. For this pattern, Oracle Service Bus provides the capability to publish a message on one JMS queue and configure a second JMS queue for the response, with a timeout value for listening for the response. This type of service appears as a synchronous service to the service consumer. Using asynchronous request/response messages has these advantages: