Menu
SOA What

SOA What

What Are the Challenges?

Security is a big one. "It's always easier to secure a closed system than an open architecture," says Silk Road's Bass. CIOs must deal with the lack of security standards for Web services (see "Calculated Risks", CIO Dec 2003/Jan 2004, page 96). To overcome some of these security roadblocks, Bass advises that companies move slowly when setting up a SOA, focusing first on business processes that don't require a high level of security.

Trying to manage the complexity of a services configuration can be tricky as well, says Bass, and requires a good SOA governance model. For example, if you have nodes on a network that are service-oriented and 100 people are using a certain interface, how do you communicate with those users if someone decides to change the interface?

Another issue is network monitoring. "As we create the capability to orchestrate complex Net-centric business processes in a service-oriented architecture, we also create complex monitoring and auditing requirements," says Bass. For instance, when a transaction goes awry on a service-oriented network, which could involve multiple service providers, finding out what went wrong or where the transaction dropped or whether someone put bad information in the network can be a challenge. "The current Web services technical standards are only beginning to scratch the surface in making these lofty service-oriented distributed collaboration, process orchestration and monitoring goals a practical reality," Bass claims.

Finally, there's the cost issue. Building a SOA isn't cheap; re-engineering your existing systems architecture is going to cost some serious money. It also requires significant human capital, including business analysts to lay out the business processes, systems architects to turn processes into specifications, software engineers to develop the new code and project managers to track it all.

Are There Any Generally Accepted Best Practices for Building a SOA?

It may sound obvious, but having a blueprint for your SOA is critical. It's very easy for companies, especially large enterprises with disparate operations, to buy new technologies or integrate applications without regard to how they fit into the overall plan. The challenge in building a SOA is to keep people - including both IT and business-side staff - focused on the architecture goals.

IT execs will also need to identify the right level of service to provide. And those services shouldn't have too fine a granularity - that defeats the goal of services, which is to function at a higher, business-process level. Too narrow a focus creates a need for more services, which increases development time. And in the worst case, too many services can flood a network.

You should also employ a SOA where it will do the most good. Bass notes that quality of service needs to be taken into account when implementing SOAs. He says that a loosely coupled architecture is good for systems that don't require near-real-time responses. Pick systems where, if information doesn't get where it needs to be on time, the consequences are minor, not catastrophic. (For example, a SOA-based air-traffic control system would be a bad idea.)

Should You Be Thinking About a SOA?

Many CIOs are seriously considering SOAs, particularly as they experiment with Web services. The potential payoffs are compelling - increased agility, faster and cheaper integration, the leveraging of existing IT assets and a focus on business processes. Sure, building a SOA requires a significant investment, and there are still plenty of questions around the immature Web services market. But, at a minimum, it's a strategy worth watching.

Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.

Join the newsletter!

Or

Sign up to gain exclusive access to email subscriptions, event invitations, competitions, giveaways, and much more.

Membership is free, and your security and privacy remain protected. View our privacy policy before signing up.

Error: Please check your email address.

More about AXA Asia Pacific HoldingsBillBillionBloombergCandle IT & T RecruitmentDana AustraliaDialogueGartnerHISIBM AustraliaNorthrop GrummanOraclePromiseSAP AustraliaSonicSonic SoftwareSpeedTandemYankee Group

Show Comments
[]