Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improve webhook resiliency #46

Closed
dillonstreator opened this issue Dec 28, 2024 · 0 comments · Fixed by #56
Closed

improve webhook resiliency #46

dillonstreator opened this issue Dec 28, 2024 · 0 comments · Fixed by #56
Assignees
Labels
enhancement New feature or request server

Comments

@dillonstreator
Copy link
Contributor

dillonstreator commented Dec 28, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request server
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant