Back to Catalog
Integration
Message Transformation
Content Enricher
The message is missing data — look it up from an external source and add it before passing along.
Intent & Description
Real-world Use Case
IoT sensor event enrichment — raw sensor reading arrives with sensorId and temperature. Enricher looks up sensorId in a device registry to add location, zone, and owner fields. Downstream analytics service receives a fully enriched event — no device registry calls needed at analysis time.
Source
📌 TL;DR
Content Enricher = fat up the message before it reaches consumers. Fetch what is missing, add it to the payload, pass it on. Cache aggressively or the external calls will kill your throughput.
Advantages
- Downstream consumers get self-contained messages — no extra fetches needed
- Enrichment logic centralized — consumers stay lean
- Can cache frequently fetched enrichment data for performance
- Enables thin producers (send minimal data) with fat consumers (receive full data)
Disadvantages
- External enrichment source becomes a dependency — its downtime blocks the pipeline
- Enrichment adds latency (external call or cache miss)
- Enriched data can be stale if external source is not the freshest
- Enricher can become a bottleneck at high throughput