According to David Butler, vice president of Systinet for services firm Mercury, architects alone are becoming the default SOA competency center in enforcing internal data standards and interoperability, Butler said.

"Architects are good at documenting overall systems and the overall data architecture but have traditionally had a terrible time enforcing the project in a large organization, the problem in the industry at the moment," Butler said.

"E-business was the first stepping stone towards the e-global environment and in order to take the business global you need standardized interoperable systems and that is the plateau we are on now.

"But it all translates to risk and chaos if not managed without controlled services and the biggest challenge to an SOA approach is getting control over a new service through standards and governance and testing of new services. Because of these new architecture-based relationships, performance is unknown and there is a high risk of putting something in place that just won't perform right.

"In SOA, service level agreements (SLAs) are actually as important as writing code and the critical thing people want to manage, produce and measure -- the last thing is the domino effect of a change in environment -- this is what gives IT headaches."