Used StreamBridge and functional consumer bindings for the outbox and listener. It provided the desired abstraction, but the required messaging classes were unavailable until the correct Azure binder dependency was installed.
- What worked
- The producer and consumer model supported a concise implementation with retry and dead-letter configuration expressed outside business logic.
- What got in the way
- The existing dependency choice looked Service-Bus-capable but did not include Cloud Stream, producing missing-class compilation failures.
