Messaging Metadata (Erl)
How can services be designed to process activity-specific data at runtime?
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.
Message contents can be supplemented with activity-specific metadata that can be interpreted and processed separately at runtime.
This pattern requires a messaging framework that supports message headers or properties.
The interpretation and processing of messaging metadata adds to runtime performance overhead and increases service activity design complexity.
Messages equipped with metadata reduce the requirements for services to contain embedded, activityspecific solution logic.