This article is more than 1 year old
SOA - dead or alive?
Can it deliver on its promises?
Comment Service oriented architectures, or SOAs, have been positioned as the great leap forwards in how IT will finally come to be the major facilitator to the business.
However, uptake around the world remains mixed, and the levels of understanding that Quocirca finds in organisations as to what constitutes an SOA remains relatively low, especially within the business community.
Discussions with vendors in the SOA space show that they also find getting the SOA message across is difficult.
This has led many parts of the analyst and press community to start predicting the death of SOA, that it has been just another architectural move on the vendors' part to try and get businesses to spend yet more money on technology for technology's sake.
Whereas in some cases this may have an element of truth, those companies that have made progress with introducing true SOA have been seen to enjoy greater business flexibility, cost savings, and ease of technical management.
The problem is that for every successful SOA implementation, there seems to be 10 that are providing few of the desired benefits. Many of these failures are down to poor understanding of the underlying principles of SOA; in particular, in the use of "loose coupling" of services. Here, the various technical functions that make up an SOA are made available as individual items that can be called by other functions on an ad-hoc basis.
This needs a scalable registry of functions that can manage the negotiation and agreement of the calling service's needs and the called service's capabilities - and many organisations have found the concept difficult to understand, and harder to implement.
Many of these organisations have then implemented a more "tightly coupled" approach, with services being tied more directly to each other. This mitigates the need for the negotiation of need and capability, but also means that each new solution has to be made aware directly of what services it can utilise - and this means that functional reuse is minimised.
This is not the only problem, and another growing area of concern that Quocirca has become aware of is in how SOA is regarded by both the business and IT; whether it is seen as a strategic project, or a strategic aim across many projects.
As an example of the differences that Quocirca has seen in SOA understanding and adoption, let's take two, very broad-brush, views within Europe. SOA adoption in Scandinavia is fairly broad, whereas adoption in the UK remains relatively piecemeal. Both geographies are working from a relatively strong financial base, and are facing similar business issues - so why the difference in SOA progress?
Quocirca believes the main difference lies in how SOA is perceived both within the business and the IT department.
In Scandinavia, the business and IT tend to be very well aligned, and SOA is being viewed as an inherent part of new solutions. The business couches its needs in process terms, and IT looks at how these new process needs can be facilitated - from a combination of existing and new functions.
These new projects coming through are still being viewed as independent, stand-alone items, with integration into other existing parts of the infrastructure being carried out as necessary. This is the "tactically strategic" approach; each project is essentially tactical, in that it is run to solve a specific problem that the organisation is struggling with at a specific time. The viewpoint is strategic in that as each of these projects completes, a long-term view has been taken around SOA, and each new solution can automatically interact with other SOA-based solutions.