“SOA Principles of Service Design” by Thomas Erl is an encyclopedia of service design principles needed to build SOA solutions. This article contains three supporting practices taken from the book: Service Profiles, Vocabularies, and Organizational Roles.
Service Oriented Architecture (SOA) has been widely accepted as an approach that facilitates business agility by aligning IT with business. In this article, Rathina Dhandapani, highlights key best practices in an SOA initiative to identify, validate and verify service inventory content well before implementation.
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. 1
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. 1
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