16 ms·
You don't need a queue to protect from Svix downtime. It can be as simple as logging failures to svix (when they happen), and replaying these events. Though as
by tasn 5y ago
You don't need a queue to protect from Svix downtime. It can be as simple as logging failures to svix (when they happen), and replaying these events. Though as I said elsewhere, this scenario is something you'd need to deal with Twilio and SendGrid too.
As for what this service does that is not basically a curl loop with an error check: see the rest of the comments. People chimed him from their experience better than I could have said it myself. Or even look at https://svix.com https://svix.com and see what we offer, you'll see that there's much more nuance. :)
We know that people underestimate webhooks, it's a challenge we need to overcome, but there really is more to it than just a POST request.
- SahAssar 5y ago> It can be as simple as logging failures to svix (when they happen), and replaying these events That's a manually implemented queue, right? I looked at the site and this thread and I still don't get it, I don't think I underestimate webhooks, but rather that I don't see why adding another webhook inbetween will help.
- tasn 5y agoIt's more of an append-only failure log than a queue, which is a whole different beast... Though as I said elsewhere in the thread, the actual delivery is just part of what we do.