Looking for SOA in All the Wrong Places?

February 5, 2009
188 Views

Systinet’s founding CTO and my friend Anne Thomas Manes pronounced the demise of SOA a few weeks ago. Honestly, SOA lost its meaning for me on the day when good, old Solaris became the “SOA operating system”. But is SOA dead or not? I don’t believe so but I think that Anne and others are looking for SOA in the wrong places. Here is why:

Part of our Systinet SOA pitch was this truism: “SOA is not something you can buy”. We believed that SOA didn’t come in a box and companies have to invest time and money to build it. And maybe this is the crux of the problem. What if the act of building internal service blueprint is beyond the capabilities and budgets of the individual customers? Go to the SOA mailing list and try to understand how to build your own SOA and you can spend the rest of your life reading the discussions and related blogs and comments.

My point is that IT departments will always spend most of their budgets keeping the lights on and there is not enough money left for a complete architectural redesign. And even if they decide to throw more money at it they will still not get it right because of lack of internal expertise, lack of vision and simply because it is too hard to

Systinet’s founding CTO and my friend Anne Thomas Manes pronounced the demise of SOA a few weeks ago. Honestly, SOA lost its meaning for me on the day when good, old Solaris became the “SOA operating system”. But is SOA dead or not? I don’t believe so but I think that Anne and others are looking for SOA in the wrong places. Here is why:

Part of our Systinet SOA pitch was this truism: “SOA is not something you can buy”. We believed that SOA didn’t come in a box and companies have to invest time and money to build it. And maybe this is the crux of the problem. What if the act of building internal service blueprint is beyond the capabilities and budgets of the individual customers? Go to the SOA mailing list and try to understand how to build your own SOA and you can spend the rest of your life reading the discussions and related blogs and comments.

My point is that IT departments will always spend most of their budgets keeping the lights on and there is not enough money left for a complete architectural redesign. And even if they decide to throw more money at it they will still not get it right because of lack of internal expertise, lack of vision and simply because it is too hard to rebuild systems that somehow “work”. Every company seems to have a set of requirements that none of the commercial products can ever satisfy and as a result the existing internal architectures are usually completely proprietary. And sediments of bad architectural decisions are nearly impossible to peel off…

Maybe it’s time to forget about this SOA delusion and look someplace else. For companies like Google, Amazon, Workday and others (including my company – Good Data) SOA is not only “yet another IT initiative” but the key differentiator that allows them to deliver a flexible and extensible set of services. And the only way IT departments will be able to “buy SOA” is to use services from the companies in the cloud. The role of proprietary internal architectures will diminish over time as companies move to an increasing number of on-demand services – and that is probably what Anne wanted to say when she declared SOA dead…

      


Link to original post