Abstract
Asynchronous messaging is the strategy of choice for loosely coupled, service-oriented architectures because it overcomes the inherent limitations of remote communication, such as latency and unreliability. Unfortunately, asynchronous messaging is not without pitfalls and requires developers and architects to rethink some of the basic assumptions they are used to when developing monolithic, object-oriented applications.
This tutorial establishes an intuitive design notation and vocabulary for asynchronous, message-based solutions to help integration architects and developers express solution alternatives and trade-offs in a technology-independent manner. The vocabulary is then used to discuss common integration problems and find alternative solutions. The patterns apply to a range of technologies, including JMS and asynchronous Web services interfaces, such as JAX-RPC.
http://www.eaipatterns.com
Date and Time
Audience
< Novice >
Speaker
