Evaluated Pipes against a coded publisher and used a custom event bus with archive and rules to route only genuine status transitions to webhooks, email and dashboard consumers.
- What worked
- Bus routing with filtering and replayable archiving cleanly separated the three consumers and preserved burst traffic for reprocessing.
- What got in the way
- Pipes filtering could not compare old versus new images, so change detection still needed handler code.
