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


Service Agent (Erl)


Home > Service Messaging Patterns > Service Agent

How can event-driven logic be separated and governed independently?  

Problem

Service compositions can become large and inefficient, especially when required to invoke granular capabilities across multiple services.

Solution

Event-driven logic can be deferred to event-driven programs that don¡¦t require explicit invocation, thereby reducing the size and performance strain of service compositions.

Application

Service agents can be designed to automatically respond to predefined conditions without invocation via a published contract.

Impacts

The complexity of composition logic increases when it is distributed across services, and event-driven agents and reliance on service agents can further tie an inventory architecture to proprietary vendor technology.

Principles

Service Loose Coupling, Service Reusability

Architecture

Inventory, Composition
 

Two service agents replace the need for the explicit invocation of utility services E and G. By deferring common logic to service agents, the overall quantity of explicitly invoked services decreases.
Audio Podcast
This pattern is discussed as part of the audio podcast:

Versioning in SOA
 

Related Patterns in This Catalog

Asynchronous Queuing (Little, Rischbeck, Simon), Atomic Service Transaction (Erl), Canonical Resources (Erl), Exception Shielding (Hogg, Smith, Chong, Hollander, Kozaczynski, Brader, Delgado, Taylor, Wall, Slater, Imran, Cibraro, Cunningham), Intermediate Routing (Little, Rischbeck, Simon), Message Screening (Hogg, Smith, Chong, Hollander, Kozaczynski, Brader, Delgado, Taylor, Wall, Slater, Imran, Cibraro, Cunningham), Message Metadata (Erl), Partial State Deferral (Erl), Partial Validation (Orchard, Riley), Service Messaging (Erl), State Repository (Erl), UI Mediator (Utschig, Maier, Trops, Normann, Winterberg), Utility Abstraction (Erl), Validation Abstraction (Erl)


Related Patterns in Other Catalogs

Event-Driven Consumer (Hohpe, Woolfe)


Related Service-Oriented Computing Goals

Increased Vendor Diversification Options, Reduced IT Burden

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.
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-2009
SOA Systems Inc.