Commit Delivery Work With Business Changes

Context

Rooms, notices, acknowledgements and subscriber effects follow changes to governance records. Durable database work reduces the gap between a successful change and delivery, but does not make every outside action atomic.

Decision

The proposed boundary commits durable delivery work with the business change and dispatches it afterward, while the current ballot call and communication-object preparation still occur inside write transactions.

Alternatives Considered

Invoke providers synchronously while holding business locks. Slow calls lengthen the transaction and can make the business write fail.

Commit and then make an unrecorded request. A process failure between those steps would lose the work.

Consequences

Delivery can repeat, so recipients and providers must recognize stable request keys. Room and acknowledgement outboxes have no attempt cap or dedicated terminal-failure alarm. The communications boundary writes its queue pointer in the business transaction, while preparing the stored object can happen before commit.