svix-webhooks VS public-apis

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

For inspirations on what type of agents I should build, I turned to the Public APIs GitHub repository which has a curated lists of free APIs. I narrowed my search for an API that does not require sign-up or an API key and returns useful information. I ultimately decided to use the Free Currency Exchange Rates API, which seemed promising upon some basic testing.

✅ public-apis/public-apis : https://github.com/public-apis/public-apis

Public-Apis Github Repo — A list of free public APIs.

Interesting thread at https://github.com/public-apis/public-apis/issues/3104

Use curl to access a free public API and get a random joke, cat fact, or whatever.

I remember the forking of https://github.com/public-apis/public-apis and the long git issue discussions. The company owning the repository stopped maintaining it but didn't give up control either. Over the years you've put in a lot of work in publicapis.dev and that is much appreciated.

Also, that isn't really a list of "contributors", but of "organisations with the most stars". Those are different things.

For example "public-apis"[1] didn't "contribute" anything as that's not a person, and looking at GitHub[2] there are a bunch of substantial contributors (the person who created the organisation/repo only has 12 commits by the way);

[1]: https://opensource-heroes.com/o/public-apis

[2]: https://github.com/public-apis/public-apis/graphs/contributo...