Burton Group recommends that, to succeed with SOA, enterprises must address all three, one technical; two behavioral:
SOA infrastructure: The Web services framework may be appropriate for building point-to-point connections, but it's not quite ready for true SOA. Advanced capabilities -- particularly policy-based management and control -- are still being defined. For the moment, an enterprise must adopt proprietary policy administration and enforcement solutions until policy standards mature.
Design: SOA requires a different approach to application design; therefore, an enterprise must train developers in SOA design principles and best practices.
Culture: Most organizations' incentive systems are in opposition to SOA; therefore, an enterprise must institute new incentives to encourage the adoption of SOA.
Burton Group research director Anne Thomas Manes says: "Despite agreement that SOA will enable better flexibility and agility, there's still debate as to what exactly SOA is and how to implement it. As an architectural style, SOA is a set of design principles and best practices whose goal is to develop reusable services."
The report details how, while core concepts behind SOA focus on loose coupling, the industry has not yet codified SOA principles and practices into well-defined design patterns. It concludes practitioners are still learning, and raging debates prevail.
"The road to SOA is not so smooth," says Manes. "SOA requires good planning and willingness to change."