Return to Home Page
Overview
    History
    Acknowledgements
    Podcasts
    Notification Form
    Feedback Form
    Press Release #1
    Press Release #2
    Press Release #3

Master SOA Design
Pattern Catalog
    Master Pattern List (alphabetical)
    Master Pattern List (by category)
    Master Pattern List with
Page Numbers (PDF)
    Master Pattern List (Text)
    Pattern Notation
    Pattern Profiles
    Symbol Legend
    Pattern Contribution Form

SOA Candidate Patterns
    SOA Patterns Review Committee
    Candidate Patterns Overview
    Candidate Patterns List
    Candidate Pattern Contribution Form
    Candidate Pattern
Feedback Form
    SOA Pattern Template

Design Pattern Basics
    What's a Design Pattern?
    What's a Design Pattern Language?
    What's a Compound Pattern?

Supplemental
    SOA Patterns and Application Technologies
    SOA Design Patterns Historical Influences
    SOA Design Patterns and Design Principles
    SOA Design Patterns and Design Granularity
    Legal

Resources
    Design Patterns Publications
    Reference Posters
    SOAPrinciples.com
    WhatIsSOA.com
    SOA Visio Stencil


Policy Centralization (Erl)


Home > Inventory Centralization Patterns > Policy Centralization

How can policies be normalized and consistently enforced across
multiple services?
 

Problem

Policies that apply to multiple services can introduce redundancy and inconsistency within service logic and contracts.

Solution

Global or domain-specific policies can be isolated and applied to multiple services.

Application

Up-front analysis effort specific to defining and establishing reusable policies is recommended, and an appropriate policy enforcement framework is required.

Impacts

Policy frameworks can introduce performance overhead and may impose dependencies on proprietary technologies. There is also the risk of conflict between centralized and service-specific policies.

Principles

Standardized Service Contract, Service Loose Coupling, Service Abstraction

Architecture

Inventory, Service
 
A global policy definition (Corporate Policy.xml) is established and applies to all WSDL documents, and a further domain policy (Claims Policy.xml) is created and linked to two WSDL definitions. This new policy structure eliminates redundancy of policy content and ensures consistent policy enforcement.
Audio Podcast
This pattern is discussed as part of the audio podcast:

•  Basic WS-Policy

•  Advanced WS-Policy
 

Related Patterns in This Catalog

Contract Centralization (Erl), Rules Centralization (Erl), Service Normalization (Erl), Termination Notification (Orchard, Riley), Validation Abstraction (Erl)


Related Service-Oriented Computing Goals

Increased Vendor Diversification Options, Reduced IT Burden


Related Publications

SOA Pattern of the Week: Policy Centralization (InformIT)


SOA Design Patterns This page contains excerpts from:

SOA Design Patterns by Thomas Erl

Foreword by Grady Booch

With contributions from David Chappell, Jason Hogg, Anish Karmarkar, Mark Little, David Orchard, Satadru Roy,
Thomas Rischbeck, Arnaud Simon, Clemens Utschig, Dennis Wisnosky, and others.

(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)

For more information about this book, visit
www.soabooks.com.
Web Service Contract Design and Versioning for SOA This pattern is also discussed in the following title:

Web Service Contract Design and Versioning for SOA
by Thomas Erl, Anish Karmarkar, Priscilla Walmsley, Hugo Haas, Umit Yalcinalp, Canyang Kevin Liu,
David Orchard, Andre Tost, James Pasley

Foreword by David Chappell

(ISBN: 013613517X, Hardcover, 826 pages)

For more information about this book, visit
www.soabooks.com.
The Prentice Hall Service-Oriented Computing Series from Thomas Erl
Home    SOA Books    SOA Magazine    What is SOA?    SOA Principles    SOASchool.com    SOA Glossary Copyright © 2007-2010
SOA Systems Inc.