The EJB Advocate explores various forms of loose coupling in service-oriented
architecture, with a focus on when it is best to take advantage of the
asynchronous processing power provided by message-driven beans.
In each column, The EJB Advocate presents the gist of a typical
back-and-forth dialogue exchange with actual customers and developers in the
course of recommending a solution to an interesting design issue. Any
identifying details have been obscured, and no "innovative" or proprietary
architectures are presented. For more information, see Introducing the EJB
Advocate at the IBM developerWorks website.
Is your definition of loose coupling too tight?
Since this is the last article of 2005, this exchange about Java Platform,
Enterprise Edition (Java EE) components o... (more)