SOA Worst Practices Volume II: A Look At Governance

SOA infrastructure continues reach peak adoption levels as IT organizations look for better ways to support their operational infrastructure—and the business. Many technology leaders believe there's simply no way to escape it as company after company seek to squeeze the competitive advantage from its information infrastructure.

However, some early adopters are realizing that they didn't properly plan for SOA governance. SOA Worst Practices, Volume I focused on tactical and strategic aspects of implementing service-oriented architecture (SOA): employing SOAP standards, the limits of XML firewalls, Web-services reuse, and so on. This white paper presents cautionary tales of several organizations whose not-so-best laid plans went awry, and the best practices they should have followed.

Here are seven worst practices that you'll learn more about:

1. Governance, as a Process, Can be Checked at the Gates
2. We'll Do Anything for Our Best Customers: Even Duplicate Our Data Center
3. Divide and Conquer: Approaching Security, Management and Governance Separately
4. As Long as I Don’t Know About It, Compliance Doesn’t Matter
5. No Worries: We Know Who’s Using the Web Services that Come With Our App
6. Hey, This is a Really Cool Registry; Our Web Services Designers Will Love It!
7. No Thanks: We Have Our Own Standards and Processes Here

SPECIAL OFFER!  Register and you will also receive the white paper Why Runtime Governance Is Critical for Service-based Applications. This white paper explains why runtime governance is essential for modern, distributed, interconnected applications and what problems it solves.