SOA Governance Tips & Best Practices
Gain practical and immediate guidance from leading users, analysts and experts on how to successfully approach, scope and implement SOA Governance. Includes SOA Governance implementation examples, guidance, checklists, mistakes and tips.
| Planning A Service-Oriented Architecture |
| Five guidelines that are seen as essential to good governance: 1) Establish an SOA Competency Center. This is a cross-functional team of key people that represent different disciplines within IT. By establishing such a group you facilitate communication between the various groups, ensuring that everyone is represented and that every aspect of the SOA architecture gets proper consideration. 2) Experience is a Good Teacher. Blueprints and best practices can be very good teaching mechanisms. They are a tangible way in which everyone involved in the SOA implementation can benefit from the work that has been done before. 3) Use an SOA Repository. Services are by definition reusable and self-describing, but don't be deceived by this oversimplified view. If services are not properly documented and made accessible in a consistent manner, they could become just as unusable as some of those legacy applications. 4) Monitor Quality of Service (QoS). Bring predictability to your SOA by implementing service management facilities. What you need is the capability to maintain end-to-end visibility into your services infrastructure via the ability to define SLAs, measure services operation and response levels, analyze service usage and resource utilization patterns, and proactively be alerted of potential and imminent service failures. 5) Manage the SOA Lifecycle. Create a disciplined and well-managed SOA lifecycle. In all other areas of IT this kind of discipline is well established and maintained. SOA should be no different. |
| Internet.com |
| Ten Strategies for Overcoming the Technological Impact of SOA Governance |
| A high-quality collection of ten SOA Governance technology tips. From the Resource: "1) Include governance technology as part of your overall SOA roadmap. 2) Make sure your governance platform is agnostic with regard to service development technologies. 3) Make sure your governance platform is able to support a full range of service deployment technologies. 4) Recognize the importance of testing as part of your overall SOA governance responsibility. 5) Collect important governance-related metrics and review them regularly. 6) Track activity through multiple IT resource layers. 7) Break down the barriers between repositories and registries. 8) When selecting a governance technology product, write a well-planned, formal RFP. 9) Avoid governance tools that require code modifications. 10) Make sure that the governance tool fits into your existing IT governance landscape." |
| Robert D. Schneider, The SOA Magazine |
| SOA Governance: Balancing Process and Agility |
| "There are a number of reasons why companies do not have a robust enough governance model. Here are a few reasons that I have seen: 1) Lack complete understanding of both design time and runtime best practices. 2) Culture does not support standards and best practices. 3) Lack of funding for governance resources and tools. 4) Unrealistic deadlines. 5) Lack of executive support." |
| Mike Kavis, Catalina Marketing |
« 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | next »
