Very good nuggets of info in this reprint of a SDTimes article.
Communicating asynchronously. "Design so that a module sends the message but keeps working, aware that it's still waiting for a response and able to react if it doesn't get a response after a certain amount of time," said Hirji.
Deploying a publish-listener (also called publish/subscribe) structure for much cross-module communication. "For instance," Hirji said, "we have a piece of code whose sole job is to do nothing but receive quotes from the marketplace for all securities and broadcast these internally to our transaction processing modules. Each module listens, but it only listens for the pieces of data that it's actually interested in at that moment."Posted by Josh at August 24, 2005 12:26 AM