The hype around Service Oriented Architecture (SOA) is tremendous—it will revolutionize IT, make life easier, streamline business, and provide untold flexibility and responsiveness. Of course, it’s not quite that easy, especially when you already have layers of legacy technical architecture, a high maintenance and support burden, and rabid business clients demanding new solutions yesterday.
So, how do you realize the potential of SOA without raising expectations so high that they will come back to bite you? Which issues do you need to address first? And, what is a realistic timeline and approach?
