Expert Says SOA and Integration Connection Overhyped

Loraine Lawson

Are we being oversold on the integration value of SOA?

 

David Linthicum certainly thinks so. In his Real World SOA blog this week, he takes vendors to task for using SOA as a selling tool. In particular, Linthicum says too many vendors are just repackaging their enterprise application integration (EAI) solutions as "SOA solutions."

 

Linthicum is a renowned SOA expert -- but you may not know that, before SOA, he specialized in integration. He even wrote a book on it. So, when he says SOA and integration are too tightly coupled -- excuse the pun -- we should probably heed his warning.

 

Of course, he's also not the first person to point this out. In March, I shared how Ronald Schmelzer of ZapThink made a similar, albeit longer, argument contending that companies were confusing true SOA implementations with what amounted to EAI 2.0 projects.

 

Linthicum's biggest complaint seems to be that vendors are selling SOA short by focusing too much on integration and other tactical issues:

"... when selling into the SOA marketing, they are driving integration and not architecture, focusing more on the tactical, and not the strategic. Not as much value to the business there."

I talk a lot about SOA's potential for integration. To be clear, that's because this blog is about integration -- not SOA - so basically I try to restrict my discussion of SOA to how it relates to integration. But don't confuse this with thinking SOA is all about integration. As Linthicum points out, integration is a small part of the SOA picture.

 

Still, I don't see the problem with focusing on tactical solutions such as integration -- as long as you don't stop there. And I certainly agree it's wrong to call something "SOA" when it's really EAI, re-branded.

 

I guess the moral of the story is simple: If you're looking for an integration solution, focus on integration. If you happen to be moving to SOA, then look into how it affects integration, but don't make that your only reason for SOA. Know what you're buying ... and don't pay a premium for an EAI solution, relabeled as SOA.



More from Our Network
Add Comment      Leave a comment on this blog post
May 14, 2008 5:09 AM Jean-Jacques Dubray Jean-Jacques Dubray  says:
Loraine:I agree with you and Dave. The short history of SOA is that vendors delivered a message and built products around different contexts: B2B, EAI, BPM, Interop, Web 2.0. The reality is that you are not doing SOA each and every time you can send a message from point A to point B. Services are reusable IT assets that can be composed in different IT solutions. This cannot happen serendipitously, you need some technology (including a programming model) and you need an approach to design assets that are reusable.SOA will actually reduce the need for EAI by definition, i.e. if you can create assets that can be reused, you will limit "duplicating-assets-and-synchronizing-data". Reply
Feb 5, 2009 12:06 PM Jim Hammett Jim Hammett  says:

Loraine- How would you say SOA-style integration differs from EAI-style integration?

Reply

Post a comment

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

null
null

 

Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.