1. Aug 14th, 2008

    SOA and the statistical non-FAIL

    I’m shocked, absolutely shocked to find out that ”corporate software development in a state of dysfunction marked by budget woes, protracted project lengths, and dissatisfied end users.” Simply ubelievable.

    In particular, I find it hard to digest that ”more than one-third of projects are abandoned after being implemented, and only 37 percent of finished projects met users’ needs.”

    Of course, none of these numbers changed much since disks filled up whole rooms and blog posts were punched into cards, but still, it’s shocking to find out that this year’s industry average is the same as last year.

    End sarcasm.

    With that in mind (via Stefan Tilkov):

    IT pros have expressed skepticism about SOA’s promised return on investment. A 2007 InformationWeek Web survey of 278 IT pros found that 32% of those using SOA said those projects fell short of expectations. Of those, 58% said their SOA projects introduced more complexity into their IT environments, and 30% said they cost more than expected. Out of all respondents using SOAs, just 10% said the results exceeded expectations.

    Hold on a second. 32% fell below expectations. 10% surpassed expectations. It gets better:

    InformationWeek’s survey results were confirmed in an August 2007 report by Nucleus Research, which found that only 37% of 106 organizations it surveyed actually were realizing ROI from their investments in SOA technology and programming.

    Considering industry standard, that doesn’t look all that doomy or gloomy. It looks … just average. So what’s the big FAIL behind this InformationWeek article? SOA. The silver bullet to heal all ails? WOA.

    Wait, but I’m a badge-wearing member of the of the RESTitecture police. Shouldn’t I be cheering any article that’s proposing an end to the unnecessarily complex WS-*?

    Not if it’s lying with statistics.

    From all my sources, it looks like SOA worked out as well as you can expect any good technology to work out. And I’m going to share a secret with you. Keep it private. REST is no silver bullet either. Five years from now, you’ll read the exact same article, only this time using the same failure rate and ROI, just blaming a different technology.

    You can’t expect anything else. No technology will ever make up for unskilled developers, immature products, bad methodologies, unrealistic requirement documents and incompetent management. The industry average is average for a reason.

    What will change is not the rate of success. What will change is the ability of the successful to do more interesting things, and do them better.

    Fifty years ago we had to walk punchcard boxes from one room to another, now we trade messages with people on the other side of the globe. With spellchecking!

    Back then we kept a rolodex with hand written scribbles and stapled business cards, today we have tools that update our rolodex in real time.

    That’s where the change is. The possibilities you can realize.

    What didn’t change is the industry average. And the average article using statistics out of context to make a point that sounds good but doesn’t say anything. There are other things horribly wrong with this article, but this one point stood out because, as fallacies go, it tends to propagate wide and far.

    1. Aug 14th, 2008

      Bob Erb

      You’ll never make it to the IT corner office being reasonable like that.

      Maybe the biggest problem with SOA is how it was swallowed and re-sold as the solution to all IT’s problems — and this time, not just the latest airplane-seat-pocketed business-at-30000-feet overview don’t-get-stuck-in-the-details magazine-approved panacea, but this time really, the one true one, the one to end all trouble, the one to free us to do what we’ve always wanted to do (whatever that is); oh, how the shiny, shiny bullet shines! No more integration issues, no more duplicate (yet somehow conflicting) data, hell, we could even get rid of those snotty local developers and offshore everything to Lower East Calcutta when everything’s just services.

      Ideas like SOA are dangerous in that they seem so simple, they slip so easily into big wigs’ heads, where they inhibit seratonin re-uptake a bit, from 9 to 5, Monday through Friday, until results equivocate, the ever-present shadow of doubt darkens, and the shine dulls on the big wigs’ big shots as even bigger shots watch them miss their mark; this is the dark night of the IT director’s soul, which lasts — unfortunately, I suppose — only until the next new thing twinkles out of some vendor-sponsored, high-concept summary in some evil, vendor-sponsored, high-concept so-called trade rag.

      I appreciate your realistic, informed, and historical perspective. You have my sympathies.

    2. Aug 15th, 2008

      Anonymous

      Ha ha brilliant! This will be the third SOA project I’ve had the ‘experience’ of in 4 years that’s headed/ing for the skids.

      You’re opinion about the common denominator of failures being ‘the usual’ and the level of incompetence of the management team is astonishingly ill-informed! It’s not JUST incompetence… in fact I’d put a bigger bite of this particularly fruity cherry into a few personality failure types:

      1.1. “I think I know about IT cos my mate’s an architect, plus! I’ve got a family webpage AND I coded 20 years ago before I became a manna-ja”.

      ii. “Careful when I turn round in case I hit you with my obvious agenda. Oh, and excuse me while I try and extracate myself from the derriere of my solution enterprise trek architect consultant adonis and new bestest mentor/pal who’s sold you the sucker you are with his techy sexy goodness”.

      18: >- “Holy sh*t, I can’t believe they didn’t realise that past my amazing interview charisma and confidence, I’m a borderline sociopath who seems to somehow fly under the radar of the people who should fire me before I burn the place to the ground.”

      If there’s a big spaghetti monster in the sky may he bless the ‘experienced’. Great article and comment, thanks!.

    3. Aug 15th, 2008

      Paul W. Homer

      I think that the technology does, in a gentle way, amplify its surroundings. A significantly better technology is easier to build and deploy causing better results. It can make a different. We see some of that in the industry, as you mention, but my sense is that we’ve always been falling far short of the actual potential of computers. We don’t see it as often as we should.

      In the short-term I think you’re correct, all of the current popular technologies are just variations on each other. The real problems, the fatal ones, are people and process. It’s not what we are building that is failing, it is how we are doing it. But, that’s a dirty little secret that programmers don’t want to mention, isn’t it?

      Any technology that proposes to be a silver bullet because it breaks everything down into manageable chunks, fails precisely because the chunking system fails to scale. A few little pieces is reasonable complexity, a million of them is a nightmare. Again and again success has been proclaimed, when in fact for any real system, it only intensifies the problems. The mistake: building it is only a fraction of the battle, fixing it when it breaks is the real problem we need to solve.

      Paul.
      http://theprogrammersparadox.blogspot.com

    4. Aug 16th, 2008

      Chipping the web: August 15th from 17:31 to 18:06 — Chip’s Quips

      [...] Labnotes » SOA and the statistical non-FAILTrue. True enough to raise Reg from his blogging grave.Tags: none [...]

    5. Aug 25th, 2008

      Rob Eamon

      SOA is not a technology.

      WS-* != SOA.

      WOA is a form of SOA, by definition. Gartner/Gall states: WOA = SOA + WWW + REST

      REST and SOA are not diametrically opposed. An SO architecture can also be RESTful.