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
The first pass at adding webhooks cut some corners as it relates to retries and delivery guarantees. The current system treats the webhooks a fire and forget. This is fine most of the time but for webhook-receiving systems that need better guarantees, this project should aim to raise the bar on delivery guarantees.
The initial issue suggested using bullmq #8 but there is an issue that prevents a trivial drop-in to the existing system with atomic queueing and stronger delivery guarantees. However, even with this, moving to bullmq as a fire and forget queueing mechanism and async processor would be a much more resilient approach than what exists now.
The text was updated successfully, but these errors were encountered:
The first pass at adding webhooks cut some corners as it relates to retries and delivery guarantees. The current system treats the webhooks a fire and forget. This is fine most of the time but for webhook-receiving systems that need better guarantees, this project should aim to raise the bar on delivery guarantees.
The initial issue suggested using bullmq #8 but there is an issue that prevents a trivial drop-in to the existing system with atomic queueing and stronger delivery guarantees. However, even with this, moving to bullmq as a fire and forget queueing mechanism and async processor would be a much more resilient approach than what exists now.
The text was updated successfully, but these errors were encountered: