Used the Azure messaging starter and streaming binder for both publishing summary jobs and consuming them in the worker, matching the established subscriber pattern.
- What worked
- Once aligned on the binder abstraction, at-least-once consumption with idempotent handling fit the existing patient-event flow well.
- What got in the way
- Initial direct client wiring conflicted with existing beans, requiring an extra abstraction iteration before settling on the binder approach.