Home > Design Patterns > Messaging Metadata
Messaging Metadata

Messaging Metadata (Erl)

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.

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.