Untitled Document
The reincarnation of SOA
To use a time-honored IT tradition of turning nouns into verbs, I have been
Rip Van Winkled. I was out during January recovering from shoulder surgery,
and when I finally felt up to catching up, the first thing I saw was that SOA
had been pronounced dead. I might as well have been asleep for years. Anne
Thomas Manes called the time of death Jan. 1, 2009. According to Anne, the
cause of death was that "SOA failed to deliver its promised benefits. After
investing millions, IT systems are no better than before. In many organizations,
things are worse: costs are higher, projects take longer, and systems are more
fragile than ever. The people holding the purse strings have had enough. With
the tight budgets of 2009, most organizations have cut funding for their SOA
initiatives."
I obviously had some catching up to do. Frankly, I was a bit shocked, as anyone
might be hearing about the sudden and untimely passing of an associate. Why
now? I agree that to date, the lack of experience, methodologies and skills
has made SOA too complex for the average organization. But is declaring it dead
and gone the right approach, especially as organizations need to become more
agile in this dire economic climate? With resources and funds shrinking, companies
need to take a very long and hard at their survival strategy. Does their strategy
put them in a position to move forward with new opportunities as they arise
-- or is it only about survival?
If increasing business agility and cutting costs are important to you, click here.
The wake
Dana Gardner
hosted a wake of sorts with Anne
Thomas Manes, David
Linthicum, Tony Baer,
JP Morgenthal,
and Joe
McKendrick. Thomas Manes cited economic reasons for ringing the SOA death
knoll: "If you are an IT group and you are trying to get funding for some
projects -- and you go forward with a proposal that says we need to do SOA,
because SOA is good, it's going to get shot down. Instead, what you have to
go forward with is very specific value." She suggested focusing on services,
but when Gardner asked whether that means we're still going to head toward SOA
through a variety of tactical measures, her answer was that you still need to
have a strong architectural group. In fact, she stated that one of the primary
reasons that SOA initiatives fail is because organizations don't actually do
the architecture. Instead, they just do service-oriented integration.
-1-