You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is a catch-all for the automatic webhook retries feature
The ability to automatically attempt retries is a useful feature that can greatly reduce the amount of recovery work necessary for downstream webhook consumers. This can generally be implemented using a message queue with a visibility timeout, such as AWS SQS.
Design document
The design document should address the following:
Determine the queue message format, keeping an eye on future extensibility, such as retries with attachments
Identify and addressing risks to the system, such as potential for cascade failure
Clear communication to users of expectations and conditions under which retries will take place, to be spelled out in guide.form.gov.sg
Describe the configuration of both the messaging queue as well as the dead letter queue (DLQ)
Key metrics for monitoring for alerts, such as the number of messages in the DLQ
Recovery procedures for managing dropped messages
The text was updated successfully, but these errors were encountered:
@syan-syan yup but there isn't an issue open for the implementation yet, so we can either convert this issue to include implementation or open a new one
karrui
changed the title
Design document for webhook retries
Automatic webhook retries feature
May 31, 2021
The ability to automatically attempt retries is a useful feature that can greatly reduce the amount of recovery work necessary for downstream webhook consumers. This can generally be implemented using a message queue with a visibility timeout, such as AWS SQS.
Design document
The design document should address the following:
The text was updated successfully, but these errors were encountered: