When I talk about SOA, Service Oriented Architecture, most of the time people as well business as developers see this as a huge investment in knowledge and technology.
When talking about the ROI of SOA, I often hear that it’s only a solution for huge companies that can invest in these kinds of technologies.
This means that SOA still isn’t very clear for people and they all tend to have the same question … what’s in it for me, for my company and how much will this cost.
Well first all, SOA isn’t the word to use, it’s all about integration. When you’re talking about data integration, business process integration, application integration, … everything has got to do with the basic principles of a SOA methodology: Loose coupling, re-use, standardization and services.
There’s no such thing as a SOA Architecture, it’s more a new way of thinking, a methodology to guide you through getting acquanted with this new paradigm.
A quote I found very useful (more information regarding the article, can be found on searchsoa):
Today’s SOA projects are largely about integration. The top benefits
organizations hope to achieve are improved data integration (32%), enable legacy
application integration (32%) and integrated disparate department applications
(23%), followed by cost cutting (21%). Staying competitive (8.4%) and driving
innovation (8%) tracked low on the expected benefits list.
More information regarding integration-projects and how to achieve improvement in these different domains will be posted regularly on this blog-post.