Brighter
Brighter copied to clipboard
[Feature] Outbox - Data Retention Policy
I would like to add the following functionality to the outbox
- A Retry counter (for explicitly clearing) so that if there is an issues that stops the message from being cleared it can then be pushed to the back of the queue (I have had a time before where the top 100 messages in the outbox were problematic and it kept attempting to clear them to no avail)
- An option that allows us to schedule a future message (This could be either using the transport (I know ASB supports scheduled messages, or using the implicit clearing sweeper)
@iancooper What are you thoughts on the above
So I suspect this really relates to an overall idea around "Outbox Data Policy"
There are a number of things you may want to configure:
- Retention policy -> What happens to messages as time passes. When do we delete sent messages or unsent messages
- Message priority -> Do we want to allow you messages to be ordered by priority for retries
- Circuit Breaker/Retry policy -> Do we invoke a circuit breaker after certain number of retries fail? Do we eventually give up on you after x retries
Suggestion: What am I doing for Large Message Payloads is writing up an ADR that we can discuss, that may help once you have enough feedback