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 (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


Messaging Metadata (Erl)


Home > Service Messaging Patterns > Messaging Metadata
How can services be designed to process activity-specific data at runtime?  

Problem

Because messaging does not rely on a persistent connection between service and consumer, it is challenging for a service to gain access to the state data associated with an overall runtime activity.

Solution

Message contents can be supplemented with activity-specific metadata that can be interpreted and processed separately at runtime.

Application

This pattern requires a messaging framework that supports message headers or properties.
Impacts

The interpretation and processing of messaging metadata adds to runtime performance overhead and increases service activity design complexity.

Principles

Service Loose Coupling, Service Statelessnes
Architecture

Composition




Messages equipped with metadata reduce the requirements for services to contain embedded, activityspecific solution logic.


Related Patterns in This Catalog

Asynchronous Queuing (Little, Rischbeck, Simon), Atomic Service Transaction (Erl), Canonical Protocol (Erl), Compensating Transaction (Utschig, Maier, Trops, Normann, Winterberg, Loesgen, Little), Data Confidentiality (Hogg, Smith, Chong, Hollander, Kozaczynski, Brader, Delgado, Taylor, Wall, Slater, Lmran, Cibraro, Cunningham), Data Origin Authentication (Hogg, Smith, Chong, Hollander, Kozaczynski, Brader, Delgado, Taylor, Wall, Slater, Imran, Cibraro, Cunningham), Intermediate Routing (Little, Rischbeck, Simon), Reliable Messaging (Little, Rischbeck, Simon), Rules Centralization (Erl), Service Agent (Erl), Service Callback (Karmarkar), Service Grid (Chappell), Service Instance Routing (Karmarkar), Service Messaging (Erl), State Messaging (Karmarkar), Stateful Services (Erl)


Related Service-Oriented Computing Goals

Increased Intrinsic Interoperability, 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.
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-2011
SOA Systems Inc.