Synchronous interaction falls short of many real-world business requirements, and that explains why supporting asynchronous message exchange has been a must-have in any widely-accepted technologies. Service Oriented Architecture(SOA) is not an exception, and it is asynchronous services that can bring out the fullest potential of SOA. It enables SOA to provide richer Message Exchange Patterns(MEP) beyond simple request-response or one-way interactions, which is the case when relying solely upon synchronous messaging. This session goes over common use cases in which asychronous messaging can be useful or necessary, including but not limited to - long running services whose processing time can go beyond time-out of the underlying transport - batch processing of requests at a certain time of the day - human intervention of requests when users should be a part of responding to the incoming messages - multiple responses for a single request where the business acknowledgement or state update messages can be sent out before the final response Manoj Kumar will join me as a co-presenter, who has been working on web service stacks including asynchronous web services.