img
Home > Design Patterns > Messaging Metadata

Messaging Metadata (Erl)

How can services be designed to process activity-specific data at runtime?

Messaging Metadata

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.

Architecture

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

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

Module 7: Advanced SOA Design & Architecture with Services & Microservices

This pattern is covered in SOACP Module 7: Advanced SOA Design & Architecture with Services & Microservices.

For more information regarding the SOA Certified Pofessional (SOACP) curriculum,
visit www.arcitura.com/soa.

SOA Design Patterns

This page contains excerpts from:

SOA Design Patterns by Thomas Erl

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

For more information about this book, visit www.arcitura.com/books.

Web Service Contract Design and Versioning for SOA

This page contains excerpts from:

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

For more information about this book, visit www.arcitura.com/books.