Interface IInboxTransactionScope
An opaque handle to a provider-native transactional scope that enlists an inbox handler's own writes together with the processed-mark, enabling exactly-once processing on document stores whose transaction is not expressible as a BCL IDbTransaction.
public interface IInboxTransactionScope
- Extension Methods
Remarks
This is the document-store analogue of the relational ITransactionalInboxStore seam. A
relational store can hand the handler a BCL IDbTransaction; a document store's
native transaction (for example a MongoDB IClientSessionHandle or a Cosmos DB
TransactionalBatch) has no BCL equivalent. Rather than leak a provider type into the messaging
abstraction, the store hands the handler this opaque scope. A handler that needs to enlist its own
writes obtains the concrete provider handle through a provider-specific extension method shipped by the
provider package (for example scope.AsMongoSession()), keeping
Excalibur.Dispatch.Abstractions free of any data-access dependency.
The base contract intentionally exposes no members: it is a marker for the provider-native scope. The
contract lives in Dispatch.Abstractions because the inbox middleware consumes it; the concrete
implementations and the provider-cast extensions live in the Excalibur persistence layer.