Turning up the tempo
The SOA paradigm would not have gained such overwhelming momentum if it were only a new approach to application integrationeven if it did provide improved developer productivity. What makes SOAs a tectonic shift of the IT landscape are the pressures of the modern enterprise IT environment, with its demand for ROI (return on investment) on time scales of weeks or months rather than quarters or years. Enterprise buyers increasingly realize that they cant afford to squeeze the maximum possible raw-performance-per-unit cost from core IT components. The added bang they can get from their bucks is just too small compared with the cost of the time thats needed to do so, especially since theyll pay twice: once to build an excessively tuned system today and a second time to overcome the resulting rigidity when future events demand adaptation.Shorter ROI time frames are made still more challenging by the churning of mergers and acquisitions, which make a mockery of any attempt to build homogeneous architectures. The IT architect is constantly presented with new process implementations that demand prompt and effective integration but come from someone elses playbook. An SOAs loose coupling and freedom to repurpose XML-formatted data will pay off in such situations. The action on the field To get a more visceral feel for what SOAs bring to the IT game, imagine playing in the National Football League at twice the usual speed. It would be faster, but it would still be a lumpy process with frequent stops for huddles and formations; it would still be a brittle process with only a few specific roles that could be assumed by any one player. No matter how quickly the clock might run, no one would ever mistake the result for a game of soccer. Soccer is far more characterized by continuous flow, by dynamic change in players roles and even by a high degree of interoperability, with a small number of rules and a language-independent set of referees signals enabling games to take place with teams from many different countries. Perhaps the most striking thing about SOAs is the way that enterprise demand for vendor cooperation has changed the terms of debate among IT suppliers. Past contestsfor example, between the distributed object models of DCOM and CORBAhave been as vigorous but unproductive as a debate over the relative merits of American football versus British rugby. Buyer interest in SOAs has instead driven IT vendors to a level of agreement on fundamentals and nuanced competition on details, to a degree that has rarely, if ever, been seen for any length of time. "Literally 100 percent of the worlds billion-dollar businesses have said that their future is an SOA," asserted Eric Pulier, CEO of Web services management and security company Digital Evolution Inc., in Santa Monica, Calif. "Not all are doing it yet, but all of them see that as where theyre going." Technology Editor Peter Coffee can be reached at email@example.com. Best Practices: Service-Oriented Architectures
Derive service definitions from business needs, not from IT functions
Separate business function from communication protocol to preserve loose coupling
Move incrementally with Web service pilot projects while wrapping legacy systems in service interfaces
Seek security and reliability from code libraries, frameworks and service bus environments, rather than diverting developer focus away from business needs
Check out eWEEK.coms Developer & Web Services Center for the latest news, reviews and analysis in programming environments and developer tools.
"I ask people, What do you want to accomplish businesswise?" said IBM Emerging Technologies Vice President Rod Smith in a conversation with eWEEK Labs this summer. "They tell me, Ive got a supply chain; Ive got business partners I want them to have access to my billing and other systems, and I want it to happen in 30 days. People talk about business performance before they talk about application performance, so Ive laid down a challenge to our folks to reduce the integration time down to a matter of hours."