How-to guide
Fan out to multiple targets
Sometimes one event needs to reach more than one place — your primary service and an analytics sink, or a new endpoint you're migrating to. A queue can deliver each event to several HTTP targets at once.
Single vs fanout
- Single — one target; the common case.
- Fanout — the queue holds a list of HTTP targets and delivers each accepted event to all of them.
Each target is independent
Every target carries its own URL, auth (Bearer / API key / HMAC / OAuth2), and delivery behaviour. One target failing or being slow doesn't stop the others — each has its own attempts and lands in the dead-letter queue on its own terms.
Fanout vs. routing
Fanout sends every event to every configured target. That's different from per-subscriber routing (deciding which target gets which event by type or customer) — for routing by customer, see customer context.
Related
- Reliable delivery — per-target retries and DLQ.
- OAuth2 & private_key_jwt — give each target its own auth.