Free Newsletters

   All InfoWorld Newsletters
Real World SOA | David Linthicum » SOA Article in CIO Magazine

June 16, 2006 | Comments: (0)

SOA Article in CIO Magazine


Christopher Koch, at CIO did a good write up on SOA. This article was more realistic than many articles on the topic, defining the real value and what’s really going on. I've always found that there is a bit of mystery when it comes to SOA, and the vendor hype is leading implementation reality. Old news, really, I've blogged about that over and over again. This article reflects that, but with better researched points.

A few tidbits:

First, there is really a problem there to be solved.

"A recent survey by the Business Performance Management Institute found that only 11 percent of executives say they're able to keep up with business demand to change technology-enabled processes—40 percent of which, according to the survey, are currently in need of IT attention. Worse, 36 percent report that their company's IT departments are having either 'significant difficulties' (27 percent) or "can't keep up at all" (9 percent)."

We all know this to be true, IT is not keeping up with the change of business, and IT executives are thrashing around looking for a magic bullet. In comes SOA. While it does define some newer approaches, enabling technology, and standards to leverage, at the end of the day this is integration and architecture, and that stuff is complex and hard to implement. Thus, no magic bullet.

The articles goes on to talk about the pragmatic aspects of SOA, including defining ROI, and figuring out what to do with your existing infrastructure. Which comes first, services or processes? How do you define and measure agility? I've taken on those topics with the SOA ROI work I've been doing, but to the author's point, there are not hard and fast metrics yet.

So, what have we learned? SOA is hard, expensive, and takes a lot of time. If there was anybody out there who did not understand this, perhaps you will now. It's a good thing that we are looking beyond the hype now, and there you’ll find the real value with realistic expectations. Now, get to work.



Posted by Dave Linthicum on June 16, 2006 06:53 AM


RATE THIS ARTICLE:





 

  •  
  • COMMENTS




Does anyone know how the global market perceives SOA? Do countries other than the United States have as much hype about it as we do? Also what other governmental regulatory issues get in the way of SOA around the globe?

Posted by: Collin at June 22, 2006 03:06 PM

I liked the article too. It brings some reality into the SOA hype. Too much hype creates unrealistic expectations. It would be like children playing with guns. I do, however, want to take an opposing view on a couple points.

Koch argues that complexity is the prime prerequisite for SOA. Doesn't this discount the possibility that even when MS is used, a business may need to split a process into discrete services like in the ProFlowers.com example? Modular coding practices have been around for years. Surfacing business application interfaces as services may still be required to adapt to the market, even for the smallest company. Think about examples you've sited like credit checks or other simple service calls external to large companies but provided by those small companies.

If Owens Corning is using 75% of their applications on SAP, 25% still run somewhere else either within our outside the enterprise. Interacting with those applications internally and surfacing their collective functions as a service to buyers or suppliers might be required. SAP's investment in middleware services oriented entries marks their recognition that customers must create business agility with their infrastructure. Collaboration with suppliers and buyers requires application integration, people integration, data integration, process integration, and much more. The approach or organization to this integration is what SOA suggests should be driven by business needs first not just IT complexity.

I'm sure none of the SAP examples exclusively use SAP for their integration needs. David, even you explain SOA as good architecture. Why would we preclude SOA for these companies? This makes the assumption that packaged applications are an alternative to SOA. I don’t see it that way. Customers should always buy packaged applications when possible. But as Koch pointed out, even those who subscribe heavily to packaged applications like SAP can’t deliver everything their business needs from those applications. Where does the business agility come from? If you don’t create an architecture that provides flexibility to adapt to the needs of your market, you will be passed up by your competition.

I also don't see the point about comparing centralized or decentralized companies for SOA applicability. If comapanies follow the 12 step approach that you prescribe, wouldn't that negate his point? Doesn't SOA actually facility callaboration, whether that's within a decentralized company or among several decentralized companies? One example of this is Penske Truck Leasing. Penske collaborates with GenPact, a subsidiary of GE. GenPact handles over 30 of Penske’s heavy paper-driven processes through tight collaborations utilizing an SOA "model". Another example is UPS. UPS effectively insources their buyers’ logistics services. UPS buyers like Toshiba and Nike utilize UPS to not only deliver packages but also customer support and product ordering processes. That can’t be done without systems on both sides that can adapt to change.

Posted by: Rob Coventry at June 27, 2006 05:09 PM

Technology White Papers

 

InfoWorld Technology Marketplace

» Technology White Papers Library

Technology White Papers by Topic

Technology White Papers E-mail Alert

Find out when the latest white paper is available:
 
 
» BUY A LINK NOW

Sponsored Technology Links