Service-Oriented Architecture

Unfortunately SOA is not a topic that is as straight forward and clear as all of us would like it to be. On top of that, when I see enterprises rushing on the SOA initiative, I see that as an early indicator for the disaster in making. What I had been doing in such cases and I also recommend the same to other SOA champions across the globe (who share the problem and potentially the view-point) are summarized below:

• It is utmost essential to ask and understand why a particular SOA initiative is being launched. And answers should not be in terms of 'deliverables' but in terms of 'results'. At times I found that the actual problem statement shared by the client can not be solved by SOA and there was no clarity why SOA is being considered. So beware of such mismatch of problems that client might be expecting SOA to solve.
• Next important thing to pay attention to is the scope. Is prime scope of SOA initiative limited to 'Integration/Broker' technology betterment or does it include any other enterprise domain? If its only limited to integration, then one need to ask and understand what 'results'/'differences' will this SOA initiative bring so that validity of the strategy can be established.
• If you are creating a roadmap or deployment plan for SOA, don't even think about it if there is no strategy in place. There is really no meaning of a roadmap if you have not defined a strategy that sets the direction of the entire roadmap. Defining roadmap is not such a complex thing but a roadmap that is going to drive all of SOA investments, programs and changes in the organizations, it better be based on strategic considerations.
• It is very common to see SOA programs to be heavily focused on integration platforms. Nothing wrong with it. However when considering a transformation view of the SOA program, there is a great opportunity to consider 'technology portfolio rationalization'. SOA must help enterprises simplify the enterprise landscape and hence such opportunities should be leveraged to reduce unwanted technology stack in the organization.
• I always believed and still stand by the view that there is nothing called 'SOA' solution or SOA portfolio. When there is SOA in the organization, it is nothing separate than existing elements of the enterprise eco-system including business applications, integration etc. SOA doesn't exist in isolation and has no life of its own. So it is extremely important to understand about the enterprise programs/initiatives that the concerned SOA program is tied to directly or indirectly in terms of outcomes. And if there is none, I will be little worried about the business case of the SOA program (and the money that is being put into it).
• As I mentioned in some of my previous blogs, BPM is likely to have more power to transform the organization than the SOA. In that light, when considering SOA, ensure that BPM is absolutely in the scope of the matter and is not left out as something to be looked into at a later point in time. That 'later' point in time never comes and even if it comes, it is never the same in the organization making it extremely difficult to get value out of SOA without it.
• We all need to understand that behind all good looking SOA roadmap, most likely there is going to be a huge task of legacy modernization/migration if SOA has to be a real thing in the organization. Given that, organization (and more importantly the SOA strategy consultants) need to clearly understand the landscape that will be impacted by SOA changes, nature of the change, readiness of the organization for these changes and finally the cost factors of these changes in the SOA roadmap. These are the important factors that make the SOA roadmap more real and credible.

In most of the cases that I have dealt with, I have been able to successfully add value to client's thinking process and quality of their decision making as far as SOA is concerned. So that's reason I believe this input will help larger SOA consulting community as well as organizations that are for ever in hurry to jump onto SOA, what ever that supposed to be.