SOA Building Blocks

Three years ago, Richmond, Va.-based Summit took on a major project to streamline the profusion of systems an electric cooperative was using to run its business.

Using IBM middleware, Summit built an integration architecture that allowed the client to keep its legacy applications in place and improve workflow and data exchange among them. Not long after that engagement, several of Summit's staffers attended an IBM meeting about SOA—at the time, a nascent buzzword McCubbins hadn't previously encountered.

"One of my sales guys and I look at each other and go, 'This is what we did at the co-op!' " recalled McCubbins, Summit's managing partner.

SOA has been a hot topic for years, but it's also a maddeningly elusive one. Every major software vendor has adopted an SOA strategy, and most throw the buzzword around with abandon. For solution providers looking to build a practice in the field, separating hype from reality is part of the challenge.

"It means a lot of different things to people, and a lot of people use it to sell whatever their agenda might be," said Tim Marshall, vice president of technology at Irvine, Calif., services firm Neudesic. "It's almost a solution in search of a problem."

At its core, SOA is an architectural philosophy focused on flexibly linked, business process-focused software components that leverage Web standards and services. It's the latest evolution in the ever-shifting IT landscape; major applications makers including SAP and Oracle have made the SOA design the foundation of their latest software suites. But because SOA is such an encompassing idea, it's prone to a broad interpretation—a recent Aberdeen Group survey found that 90 percent of respondents said they have or are adopting SOAs in their businesses.

Analyst Ron Schmelzer of ZapThink, a research firm specializing in SOA topics, waves off such grandiose statistics. SOA momentum is gaining, but serious SOA projects are still at the early end of the adoption curve. Schmelzer estimated that perhaps 100 textbook SOA case-study projects were carried out last year.

"Anybody who is trying to do SOA is realizing that it's a lot more involved than they might have thought," Schmelzer said. "It's pretty easy to put a Web services interface on anything, but to actually change the way you build applications so the services can consume those applications—well, that involves changing the way people build applications."

One textbook case is the modernization project that Ultramatics, Oldsmar, Fla., took on three years ago for marine transportation services company Crowley Maritime. As it grew and acquired, Crowley ended up with a hodgepodge of heavily customized, disparate systems that required resource-intensive, point-to-point adapters for integration.

Until Crowley engaged Ultramatics, it was bracing itself for a complete rip-and-replace job. Ultramatics suggested an SOA approach, using IBM WebSphere infrastructure like Message Broker and MQ to create an Enterprise Service Bus (ESB) linking Crowley's systems. The SOA revamp, which took about a year from planning to the first deployment phases, slashed the time and cost of implementing changes and bringing new systems online.

"We helped educate them that SOA is a journey, as opposed to a product that you buy," said Saru Seshadri, Ultramatics' president and founder. "It's not a one-time deal."