SOA governance Dos and Don’ts

SOA Governance is one of those things in the world of SOA that’s largely misunderstood. I can understand why, as the vendors are defining it differently. However, as SOA problem domains become more complex, typically more than 50 services, the need for SOA governance becomes even more apparent.

So, how does one select a SOA Governance solution? It’s really a matter of a few dos and don’ts.

Dos

• Do select a vendor that provides SOA governance features that are more runtime in nature. Many SOA governance tools focus on design-time features, which are fine, but the runtime features provide the most value.
• Do look at SOA governance solutions that are well integrated with testing and performance management tools. Let’s face it; SOAs are performance problems waiting to happen.
• Do make sure to do the upfront planning, and place the proper management processes around the technology.

Don’ts

• Don’t select a SOA governance vendor only because it’s part of a suite of software. It should have value as a stand-alone product, not matter if it’s bundled in a suite of software or not. For example, AmberPoint may be a better fit, for your problem domain than one of the super SOA stacks that offer everything. SOA governance is too important just to accept what comes in the bag.
• Don’t rely on what’s working within other companies. Your problem domain is unique; the SOA governance solution will be as well. Trust me.
• Don’t forget that you and your SOA governance solution will be together for a long time; thus consider the quality of the vendor, support, training, and so on. You’ll find that the better vendors provide holistic value, within and beyond the technology.
• Don’t marry standards. If there is a fit, great. Don’t wait for standards to mature before you move into SOA governance … you’ll be waiting for a long time.