Content enricher pattern By David Boyne

Content enricher pattern By David Boyne

Content enricher pattern

Sometimes downstream consumers need more information (sometimes seen when events are notification events). Downstream consumers call external APIS or back to the producer to get information they require. Be careful with this pattern as it could lead to coupling.

With content enricher pattern you can add an enricher in the middle to pick up messages/events and enrich them before sending downstream to consumers.

Why enrich messages and things to consider

  • Keeping the enrichment outside of the consumers domain, keeping consumer “pure”.
  • Stop consumers fetching information they require from producer or other APIS.
  • Enrichment pattern can lead to more code to maintain and manage
  • If consumers need more information, are your event payloads or business boundaries, correct?

Extra resources

Want to work together?

If you're interested in collaborating, I offer consulting, training, and workshops. I can support you throughout your event-driven architecture journey, from design to implementation. Feel free to reach out to discuss how we can work together, or explore my services on EventCatalog.

Download EDA Visuals

Join over 13,000 others learning EDA and download all the EDA visuals directly to your computer. This document updates everytime a new visual is added so make sure you come back to get the latest.

Download now →
Diagrams and thoughts by @boyney123 to help you learn.