We don't usually think much about Webhooks -- at least I don't. It's just web requests after all, right? In reality, there is a lot of complexity behind routing webhook requests through the internet. What if a webhook request gets lost? How do you know it was received in the first place? Can it be a security issue if a webhook gets handled twice? (Spoiler alert: yes)
Today I sit down with Tom from Svix to talk about what it takes to build an enterprise-ready webhook service. Of course it's written in Rust.
About Svix
Svix provides webhooks as a service. They build a secure, reliable, and scalable webhook sending and receiving system using Rust. The company handles billions of webhooks a year, so they know a thing or two about the complexities involved.
About Tom Hacohen
Tom is an entrepreneur and open source maintainer from Tel-Aviv (Israel) and based in the US. He's worked with people from all around the globe (excluding Antarctica). Prior to Svix, he worked as an Engineer at Samsung's Open Source Group on the Enlightenment Foundation Libraries (EFL) that are used by the Samsung backed Tizen mobile operating system.
Proudly Supported by CodeCrafters
CodeCrafters helps you become proficient in Rust by building real-world, production-grade projects. Learn hands-on by creating your own shell, HTTP server, Redis, Kafka, Git, SQLite, or DNS service from scratch.
Start for free today and enjoy 40% off any paid plan by using
this link.
Links From The Episode
Official Links
