Patterns from Thomas Erl’s book, “SOA Design Patterns”. Today, we present Chapter 16, Service Governance Patterns, comprising a number of 8 patters. Compatible Change, Version Identification, Termination Notification, Service Refactoring, Service Decomposition, Proxy Capability, Decomposed Capability, and Distributed Capability.
In this article we present 3 Inventory Governance Patterns from chapter 10 of the book SOA Design Patterns by Thomas Erl: Canonical Expression, Metadata Centralization, and Canonical Versioning. They are part of an 85 patterns catalog that serves enterprise architects and developers to find and build strong SOA solutions based on tested and proven SOA practices.
A review of Michael Poulin's book, Ladder to SOE. Michael's book shows how to use the principles of service orientation to align IT with the business, and the business with market dynamics - creating the Service Oriented Enterprise. Becoming an SOE requires new habits of service-oriented thinking and Michael points these out along with techniques for effectively using them.
This article presents a framework of SOA Governance processes, a maturity model, linked to the processes and a description of how architects should be involved in these processes.
InfoQ spoke with Clive Gee, William A. Brown, Robert G. Laird, Tilak Mitra about their latest book SOA Governance: Achieving and Sustaining Business and IT Agility.
Pierre Bonnet argues that information systems are too opaque and not agile enough. He claims this is the main reason why "healthy" companies can collapse within months as they take on too much risk. 5
This article proposes a new Message Type Architecture to help manage the message formats in a SOA. The approach promotes reuse and helps aligning the Data and SOA governance processes. 28
This article shows how recommended contract versioning design policies relate to a SOA Maturity Model. The goal is to provide a roadmap for achieving versioning and composability.
Kjell-Sverre and Jean-Jacques revisit the concept of compatible contract based on XML, XML Schema and WSDL extensibility to foster service reuse and complement Governance. 29
The hardest thing about a successful adoption of SOA is not the technology, but rather, the culture change. Todd Biske offers his perspective on using Governance to drive culture change. 1
Alex Maclinovsky explains why his vision of Governance differs from those prevailing in the industry. Based on a precise understanding SOA platforms, he defines a unified view of SOA Governance. 1
Michael Poulin explains the necessity for SOA governance to ensure an Enterprise SOA's success, relying on concepts from the OASIS SOA Reference Model and Reference Architecture.