In looking the latest stories and articles about SOA, it seems to me that many are no longer thinking about the A...architecture.

Why do I think this? Just look at the press, the focus is on the technology instances, and not the overall architectural challenges. Thus, SOA is an ESB, SOA is governance, SOA is programming, but SOA is almost never an architecture. This is a bad trend if you ask me.

Pushing this product-oriented agenda are the marketing departments at the various vendors. They don't know how to promote a notion, such as architecture, but do know how to promote a product. "SOA," the term is hot, thus they sell SOA, which to them is their product.

Therefore, there is much confusion with the end users; indeed many don't understand what SOA really is, and how to make it work. Moreover, they have simplified the concept so much that it won't do them much good and many are dragging in products looking for a quick fix that just won't happen. Remember: Think, analyze, understand, test, and then purchase the technology.

Repeat after me:

SOA is architecture, not a product.

The value of SOA is in the ability to create an agile and functional architecture which aligns with the business.

SOA requires a lot of upfront work before you select the proper technology set.

SOA is almost never a quick fix.

Sorry to stop the party, but somebody needs to say something. Focus on the A of SOA, and you'll be fine.

Posted by Dave Linthicum on August 25, 2006 06:07 AM