Wednesday, August 27, 2008

SOA adoption down from 2006 - Are you surprised?

Not me. Having read the story and a very valid perspective from Joe McKendrick . I think a point that got missed is that : wasn't this expected?

To me it was. The reason at a macro level is that time and again we have seen that "Information Technology Industry " is the definition of a cyclical industry. Just when you thought that Rational Unified Process was the silver bullet for software development , Agile methodologies came about and challenged RUP. Just when you thought that the only way to build high performance websites was by purchasing high-end Unix servers , Horizontal scalability avatar was realized via google and showed that you can put together a ton of small PC's and run a web-scale application like that of google's(note that this might change again with red-shift).

The problem in IT and business is that just about the time when you can solve a problem , it actually moves elsewhere. SOA came into existence when the mantra for doing business shifted from "Think Globally and Act Locally" to "Think Globally and execute globally" . So executing globally required lot of governance , control and to some - excessive redtape. It lead to the creation of a new position in the IT organization - VP shared services , responsible for managing all shared assets by the organization.

Now the Mantra for business seems to be "Think Globally , execute globally and Collaborate Globally" - By collaborate globally I am referring to Crowd sourcing and open source techniques. The collaborate aspect changes the IT organization structure yet again. Instead of having a business head for "shared services" whose aim in life was to own everything common used in the Enterprise , The Lines of businesses now have the option to use crowd sourcing techniques and leverage SaaS type solutions to achieve their goals. When they do that there obviously will not be any synergies between the styles of consumption of services but clearly there will be a lot of JBOWS (Just a bunch of services) . As a result in my opinion the SOA concept of coming up with a master API that will be used by everyone is failing.

Labels: , ,

2 Comments:

At 7:56 AM, Anonymous Rob Eamon said...

"...SOA concept of coming up with a master API that will be used by everyone is failing."

Interesting. I've never heard "master API" as being one of the concepts of SO.

Since SOA doesn't have a common definition used by all/most, stories such as "SOA adoption down" or "SOA failures up" or "SOA being used more broadly" are all bunk.

What is SOA to one company is JBOWS to another. Many consider to be WOA to be different from SOA--even though the creator of the WOA term explicitly defined WOA as a refinement of SOA.

I guess my point is that we shouldn't read much of anything into these adoption stories.

 
At 8:16 AM, Blogger Niraj J said...

Rob ,

Agreed that :What is SOA to one company is JBOWS to another.

What I have typically seen in Fortune 100 kinda companies is that SOA corresponds to a - central owner of common services and the SOA platform so that there can leverage across the enterprise. And hence my comment about Master API.

Now JBOWS is actually SOA , but not a definition the SOA group within an Enteprise would agree with. Well ofcourse if you do not have an SOA group in the Enterprise , the JBOWS is your SOA and there is no disagreement.

 

Post a Comment

Links to this post:

Create a Link

<< Home