Consider supporting inconsistent reads for outbox record loading

[danielmarbach]

Describe the feature.

Related to #324

Currently, all outbox lookups are using consistent-reads. Theoretically, it would be possible to allow inconsistent reads at the cost of potentially running into more optimistic concurrency violations on the same outbox record. This might be a nice cost optimization for certain scenarios.

During the implementation of the eventual consistent read support for saga lookups we have decided to scope eventual consistent reads for outbox records out because we assumed people opting into the outbox are willing to make the tradeoffs for having more consistent outbox handling given the existing overhead of the outbox anyway.

That being said, this feature can always be reconsidered, and this issue serves as a reference point to also track potential user inputs.

Additional Context

No response

[jpalac]

@danielmarbach could you please provide some scenarios where having this support would benefit the customer?

[mauroservienti]

@danielmarbach could you please provide some scenarios where having this support would benefit the customer?

Costs control. In DynamoDB, different types of reads come with different costs. Possibly, there might also be a performance benefit in certain high-throughput/low-concurrency scenarios.