Content Enricher is definitely a useful integration pattern. It allows easily enriched message content with new data gathered from an external resource. In the vast majority of Mule’s apps, I have been using the Message Enricher Component. Today, I will point out the main differences in Mule 3.x and Mule 4.x regarding this element.

Content Enricher Pattern

When you think about message processing, you have in mind a specific entity. There are times when you don’t have enough data to proceed a message further. As a result, you need some pulling and enriching mechanism. Below, you can see Enricher pattern diagram from enterprise integration patterns site/book. As you can see, the message (before entering Enricher) has smaller content. Then component looks for additional data and appends it to the original message. In consequence, you’ll have an enriched message.

Source: DZone