Learn More
Integration of applications and business processes is a top priority for many enterprises today. Requirements for improved customer service or self-service, rapidly changing business environments and support for mergers and acquisitions are major drivers for increased integration between existing “stovepipe” systems. Very few new business applications are(More)
TRADITIONALLY, SOFTWARE architects were entrusted with making “decisions that are costly to change.”1 Because these decisions often had to be made early in the project, architects drew on their experience and ability to abstract to get them right. Repeated project cost and timeline overruns have demonstrated, though, that trying to plan all features and(More)
The software development community is once again at an interesting inflection point. Distributed and interconnected systems have become the norm for new development efforts to the extent that the word "application" itself might have to be redefined. Independent variability and evolution of the interconnected components are enabled through loosely coupled(More)
Y ou know you’re a geek when going to the coffee shop gets you thinking about interaction patterns between loosely coupled systems. This happened to me on a recent trip to Japan. One of the more familiar sights in Tokyo is the numerous Starbucks coffee shops, especially around Shinjuku and Roppongi. While waiting for my “Hotto Cocoa,” I started thinking(More)
A General Retrospective Olaf Zimmermann: How did your book come to be? How did you get together, and how did you nd your contributors and reviewers? Bobby Woolf: Martin Fowler was the matchmaker. When he wrote Patterns of Enterprise Application Architecture,2 Kyle Brown pointed out that his pattern language was not addressing asynchronous messaging. Martin(More)
Y ou know you’re a geek when going to the coffee shop gets you thinking about interaction patterns between loosely coupled systems. This happened to me on a recent trip to Japan. One of the more familiar sights in Tokyo is the numerous Starbucks coffee shops, especially around Shinjuku and Roppongi. While waiting for my “Hotto Cocoa,” I started thinking(More)
Communicating inside a single program is trivial: one method calls another, the result comes back, and the calling method continues. If anything goes wrong, an exception is thrown. If the program aborts altogether, both caller and callee share the same fate, making the interaction an all-or-nothing affair. This kind of binary outcome is a welcome behavior(More)
ing and Library Use: Abstracting is permitted with credit to the<lb>source. Libraries are permitted to photocopy for private use of patrons,<lb>provided the per-copy fee indicated in the code at the bottom of the first<lb>page is paid through the Copyright Clearance Center, 222 Rosewood<lb>Drive, Danvers, MA 01923.<lb>Selected CS articles and columns<lb>are(More)