BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Governance Content on InfoQ

  • "SOA Governance" Revitalized

    This article by Miko Matsumura discusses why people are pursuing SOA, whether SOA is dead, what SOA Governance is, what the relationship is to SOA itself, how it differs from management, how SOA differs from integration, and why SOA and SOA Governance continue to be significant issues for the Enterprise.

  • Wonderland Of SOA Governance

    Michael Poulin elaborates on the differences between of governance and management and tries to explore the 'wonderland' of governance in a service-oriented environment. He defines SOA Governance, explores the relationship between governance and enterprise architecture, and discusses accountability and ownership of governance efforts, and how practitioners can instrument SOA governance.

  • A Decade of SOA: Where are we, Where are we Going?

    SOA is 10 years old. InfoQ has gathered Jeff Andres, Eric Ballou, Dave Hollander and William El Kaim, all Enterprise Architects with a long experience in SOA, to share their perspectives on where we are and where we are heading, as part of a virtual panel. They talk about Reuse, Business/IT alignment, Governance,...

  • Practices from “SOA Principles of Service Design” by Thomas Erl

    “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.

  • SOA and Service Identification

    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 "SOA Design Patterns" by Thomas Erl, Part 2

    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.

  • Patterns from SOA Design Patterns by Thomas Erl, Part 1

    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.

  • Book Review: Ladder to SOE

    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.

  • SOA Governance Maturity – an Architect’s View

    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. The authors provided some practical guidelines on how architects can lead or provide support at the various processes of the lifecycle and maturity levels.

  • Interview with the Book Authors: Brown, Laird, Gee, Mitra: SOA Governance

    InfoQ had the opportunity to review the new book “SOA Governance: Achieving and Sustaining Business and IT Agility” and interview its authors Clive Gee, William A. Brown, Robert G. Laird, Tilak Mitra.Topics covered include the role of reuse in SOA, SOA governance tooling, Business/IT alignment, etc.

  • We Need to Create Information System Ratings

    Pierre Bonnet, CTO of Orchestra Networks, argues that information systems are too opaque and not agile enough. He claims this is the main reason why "healthy" multinationals can collapse within months as they take on too much risk. He suggests that information systems be rated on how they manage master data, business rules and business processes.

  • A Message Type Architecture for SOA

    This article proposes a new Message Type Architecture based on two DSLs to help manage the message formats in a SOA. The approach promotes reuse via the Enterprise Data Model referenced in message type definitions. It also helps aligning the Data and SOA governance processes.

BT