In essence, Todd is arguing for the notion of policy design, which I agree with. If you're standing up services, and you know the publisher and the consumer of those services, then defining well-designed policies for those services is probably an excellent idea. I'm not arguing that point.
The core issue that I have is with the real value of the technology, which just does not seem to be there. The fact is, you don't need design-time service governance technology to define and define service policies.
In SOA projects and SOA-related cloud computing projects that I've been monitoring, the use of that technology just does not appear to bring the promised value to the project. Instead, they find the design features and functions within the existing runtime service governance tools work just fine. In many instances, the use of another technology or tools is counterproductive.
People often make the case to me that you can't spend too much money and time on the use of design-oriented technologies. The fact of the matter is, you can. Ultimately the market normalizes itself and any technology that does not provide good value will quickly fall out of sight. That will be the case with design-time governance for cloud computing -- and perhaps SOA overall.
This article, "Why design-time service governance makes less sense in the cloud," was originally published at InfoWorld.com. Follow the latest developments in cloud computing at InfoWorld.com.