« Need Better Legacy Integration for SOAs | Main | Is IBM Confusing Its Own SOA Market? »
September 18, 2005Oh No! Another SOA Reference Model.
You can’t beat some of the vendors in this space. They want you to purchase their SOA products, thus they must tell you how to view the notion of a SOA. So, how do you do that? Create a reference model of course, there are dozen now. One more won’t matter. Right? Other than adding to the confusion out there, this is becoming an epidemic.
So, who are the latest reference model makers? Next week, a group of software makers, including Sonic Software, AmberPoint, Systinet and BearingPoint, will announce the creation of the SOA Maturity Model white paper. You’ll find more information here.
Why? “While SOAs have been in the public eye for years, there haven't been many publications that help people explain the cost-saving benefits of an SOA to corporations. The Sonic-led paper aims to help architects articulate the cost-benefits of using an SOA to conduct business transactions.”
Hmmmmm. What about this one? Perhaps this one. Also, you can’t forget about the standards guys such as OASIS SOA Blueprints.
Come on guys. Do something original. Instead of telling people how they should think about a concept, this time SOA, tell them how your product works as a solution pattern, including where it works best, and where it does not. The users would love that.
However, Ron Schmelzer from ZapThink, does sum things up nicely. Ron said that while best practices are definitely needed to make SOA work, "all these discreet, separate efforts are confusing end users. I suggest that these folks team up with the OASIS Reference Model and OASIS SOA Blueprints teams to coordinate their efforts and make something happen in a more cohesive way that reduces, not adds, to architect confusion around how to implement SOA best." Yep.
Posted by davel at 09:05 AM in
|
Digg This |
Add to del.icio.us

Dave Linthicum's Podcast Channel
