Passed Messages | Salesforce Architects

This Level 3 documentation and implementation diagram shows an example of a process flow for the passed messages pattern that includes a publisher, a subscriber, and a message. The message is split into multiple parts, which are transformed individually and then reassembled prior to being sent to the subscriber.

Download Diagram
Open the template in Lucidchart (Lucidchart account required)

Pattern Overview

The passed messages pattern incorporates a streaming message platform to address issues like spikes in volume and complex data transformations. It works by segmenting the message handling logic into multiple components:

One component handles message routing such as determining required transformations and the final destination.
Another set of components handle different layers of message transformation (field mappings, object relationships, and so on).
The last component writes out the final, modified message.

This is a Level 3 Documentation and Implementation diagram according to the Salesforce diagram framework.

Learn more by reading the Architect's Guide to Event-Driven Architecture with Salesforce.