SOA governance dos and don’ts …or maybe not

Service Oriented Articles Articles : SOA governance dos and don’ts …or maybe not

I had a few reactions to my SOA governance dos and don'ts post of last week. And, for the first time, I agree with them. :-) Perhaps the title should have been "Looking at SOA governance technology."

Fist, I saw this from James McGovern.

"Todd Biske keeps Dave Linthicum honest regarding SOA Governance. Way too many industry analysts view SOA through the lens of products and refuse to expand the conversation. I would like to add one additional principle: Align your SOA to your enterprise information protection policies as so many so-called enterprise services miss this point."

First, he may be right about the lens of products for this particular post. Indeed that is what I had in my head as I wrote it, in reaction to an e-mail I received. Second, I'm certainly not an analyst.

Todd provided more detail:

"Dave Linthicum had a recent post called SOA Governance Dos and Don'ts which should have been titled, 'SOA Governance Technology Selection Dos and Don'ts.' If you use that as the subject, then there's some good advice. But once again, I have to point out that technology selection is not the first step.

My definition of governance is that it is the people, policies, and processes that ensure desired behavior. SOA governance, therefore, is the people, policies, and processes the ensure desired behavior in your SOA efforts. So what are the dos and don'ts?"

Actually Todd is right. The post was more about the tools and not the process or the people. However, I have enough out there about that aspect of SOA governance that for this particular post it was more narrowly focused. I should have been clearer about that.

Okay, consider myself called out and standing corrected.

Source: SOA Articles at InfoWorld.com