Features

Bits at a time

Service-oriented architecture (SOA) has the potential to do a great deal of good – as long as it’s consumed in bite-sized chunks.

01 November 2009

Could SOA finally be maturing? It seems so. Three years ago when the hype cycle was at its peak, SOA was being plugged by every enterprise vendor under the sun as a way of getting more flexibility and re-use for the customer’s software spend. Even some traditional ERP vendors said they were moving away from the large monolithic projects to more agile delivery. Instead of the large integrated project, SOA says that applications are composed of individual services, loosely coupled, and linked together with tools that allow business processes to be automated on the fly. That’s the theory anyway. SOA’s success has been mixed: it has proved an excellent way to wrap legacy applications but the re-usability has been harder than it looked in 2006.

Malcolm Rabson, MD of Dariel Solutions, says there has been success connecting islands of information. “Because SOA is such a misinterpreted term, we’ve tended to do different things. We’ve had the most success getting connectivity and interoperability between islands of data. To go further we need to get the data onto a dashboard and get it into a business process. The secret is not to do it in isolation but rather analyse the business problems and processes, and then try to make it accessible to everyone. The fact that it’s service-oriented is a by-product.”

ITWeb Premium

Get 3 months of unlimited access
No credit card. No obligation.

Already a subscriber Log in