convoy VS svix-webhooks

Yup. Even DigitalOcean still doesn't have webhooks despite several user requests see here [0]

My business is building a Webhooks Gateway for delivering webhooks at scale - Convoy [1]. We use Convoy Cloud to power Nohooks. The goal is to show what's possible with Convoy so more providers can easily provide webhooks.

[0] https://github.com/digitalocean/api-v2/issues/14

[1] https://github.com/frain-dev/convoy

Speaking with platform engineers at events, in various online communities and even within the Convoy community validated the notion that managing webhooks in production is not always easy and can require a lot of effort. Platform engineers believe strongly in frictionless self-service developer experience, and solving for efficiency to quickly provide business value. Let’s take a look at why some haven't adopted a webhooks gateway such as Convoy to manage webhook events and integrations yet and what we are doing to change that.

If you feel like this article helped you understand Webhooks better! I would be super happy if you could give us a star! And let me also know in the comments ❤️ https://github.com/frain-dev/convoy

This is precisely what Convoy does. See here: https://github.com/frain-dev/convoy. If you have any questions, the team is reachable on Slack here.

My initial reaction would be to use a self-hosted webhook relay (e.g. Convoy) that will queue / retry until my internet is back online. However, I'm a bit hesitant to throw a large dependency in the mix in the name of reliability. My other thought I had was setting up some form of load balancer, that will initially attempt to be a passthrough straight to Discord, and only if that fails, then get a queue / retry software involved?

You should check out getconvoy.io, if you're interested in our cloud platform please reach to us at [email protected]

That's exactly why we built Svix[1]. Building webhooks services, even with amazing tools like FastAPI, Celery and Redis is still a big pain. So we just built a product to solve it.

Hatchet looks cool nonetheless. Queues are a pain for many other use-cases too.

1: https://www.svix.com

Obviously Deno have vested interest it (and so do I as the founder of Svix[1]), but my take is that webhooks are great, though there are alternatives that could be better or complementary depending on the situation.

At Svix we also support running JS instead of sending webhooks (using Deno!), and it is very useful, but there are many limitations with this approach, and in general oftentimes people just want the data passed to their systems and deal with it there. Not write a bit of JS to do something ad-hoc.

So in short, like always with software engineering: "it depends" and there are tradeoffs to each approach.

1: https://www.svix.com

Svix - Webhooks as a Service. Send up to 50,000 messages/month for free.

We opted for a more manual approach, we have a ctx!() macro[1] we use for wrapping errors we want to enrich thay we use like this[2]: ctx!(some_fallible_fund(foo))?

I wodner if anyone is doing anything better? The nice thing is that we have relevant fields in our error type, so we get a full backtrace out if it.

1: https://github.com/svix/svix-webhooks/blob/main/server/svix-...

2: https://github.com/svix/svix-webhooks/blob/main/server/svix-...

This is what we do at Svix: https://docs.svix.com/receiving/source-ips

I've seen other companies (e.g. Stripe) also offer it via JSON, but I personally think it's not that important to provide it in a machine readable format if you don't plan on changing it; which you shouldn't as it'll break integrations. You should only add new IPs that can only be allocated to new customers.

P.S, if you'd like to start sending webhooks, you should probably check out Svix: https://www.svix.com

If I understand you, you just want some queue system, like kafka.But if you want a whole app who handle all your webhooks usage you can see : https://github.com/svix/svix-webhooks/

Might want to look into Svix and HostedHooks

Repository on Github: https://github.com/svix/svix-webhooks