python-ksuid VS svix-webhooks

Homepage: https://www.svix.com

It's really fast, it makes writing secure and correct code easier, it's easier to deploy and distribute (one static binary), and it's a lot more fun. :)

Webhooks are really cool, and I absolutely love what they enable. They make the web compose-able, interconnected, and enable people to automate a lot of their work! Our goal is to make them easy, reliable, and consistent, so that more services offer them and they are easier to consume.

I'd love to hear your feedback! We've incorporated most of the comments we got the last time[0] (thanks again everyone!), and we would love to know how we can improve the product further. Got any suggestions?

Homepage: https://www.svix.com

Repo: https://github.com/svix/svix-webhooks/

Docs: https://docs.svix.com/

API reference: https://api.svix.com/

[0] https://news.ycombinator.com/item?id=26399672

I wasn't going to post it here because it feels a bit small for a show HN, but then I figured: why not. :)

It's a pure Rust implementation of Segement's KSUID, and I created this library while working on Svix[0].

I haven't written any Rust for a while, so even though I have written quite a bit of Rust code in the past (see Etebase[1]), I'm a bit rusty (no pun intended).

Anyhow, I just wanted to share, and I'm hoping to get some feedback if you have any. :)

Code and examples: https://github.com/svix/rust-ksuid/

P.S, the package is tested for compatibility against the reference Go implementation.

[0] https://www.svix.com

I created this library while working on Svix. We have a highly scalable and distributed environment there, which is where KSUIDs really shine.

These reasons are exactly why we started Svix[1] (we do webhooks as a service). I wish we existed to serve you guys back when you started working on it. :)

[1] https://www.svix.com

Hey everyone, my name is Tom, and I'm the founder of Svix (https://www.svix.com) - previously known as Diahook. Svix makes it easy for developers to send webhooks from their service using a simple API. Think Twilio or SendGrid but for webhooks.

Webhooks are how servers notify each other of events, so they are a key component of many APIs such as Stripe, Shopify, Slack, Dropbox and Github.

Code and examples: https://github.com/svixhq/python-ksuid/

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