How do you build a system that handles 90 million requests per second? That’s the scale that Cloudflare operates at, processing roughly 25% of all internet traffic through their global network of 330+ edge locations.

In this episode, we talk to Kevin Guthrie and Edward Wang from Cloudflare about Pingora, their open-source Rust-based proxy that replaced nginx across their entire infrastructure. We’ll find out why they chose Rust for mission-critical systems handling such massive scale, the technical challenges of replacing battle-tested infrastructure, and the lessons learned from “oxidizing” one of the internet’s largest networks.
About Cloudflare

Cloudflare is a global network designed to make everything you connect to the Internet secure, private, fast, and reliable. Their network spans 330+ cities worldwide and handles approximately 25% of all internet traffic. Cloudflare provides a range of services including DDoS protection, CDN, DNS, and serverless computing—all built on infrastructure that processes billions of requests every day.

About Kevin Guthrie

Kevin Guthrie is a Software Architect and Principal Distributed Systems Engineer at Cloudflare working on Pingora and the production services built upon it. He specializes in performance optimization at scale. Kevin has deep expertise in building high-performance systems and has contributed to open-source projects that power critical internet infrastructure.

About Edward Wang

Edward Wang is a Systems Engineer at Cloudflare who has been instrumental in developing Pingora, Cloudflare’s Rust-based HTTP proxy framework. He co-authored the announcement of Pingora’s open source release. Edward’s work focuses on performance optimization, security, and building developer-friendly APIs for network programming.

Links From The Episode

• Pingora - Serving 90+ million requests per second (7e12 per day) at Cloudflare
• How we built Pingora - Cloudflare blog post on Pingora’s architecture
• Open sourcing Pingora - Announcement of Pingora’s open source release
• Rust in Production: Oxide - Interview with Steve Klabnik
• Anycast - Routing traffic to the closest point of presence
• Lua - A small, embeddable scripting language
• nginx - The HTTP server and reverse proxy that Pingora replaced
• coredump - File capturing the memory of a running process for debugging
• OpenResty - Extending nginx with Lua
• Oxy - Another proxy developed at Cloudflare in Rust
• Ashley Williams - Famous Rust developer who worked at Cloudflare at one point
• Yuchen Wu - One of the first drivers of Pingora development
• Andrew Hauck - Early driver of Pingora development
• Pingora Peak - The actual mountain in Wyoming where a Cloudflare product manager almost fell off
• shellflip - Graceful process restarter in Rust, used by Pingora
• tableflip - Go library that inspired shellflip
• bytes - Reference-counted byte buffers for Rust
• The Cargo Book: Specifying dependencies from git repositories - Who needs a registry anyway?
• cargo audit - Security vulnerability scanner for Rust dependencies
• epoll - Async I/O API in Linux
• Tokio - The async runtime powering Pingora
• mio - Tokio’s abstraction over epoll and other async I/O OS interfaces
• Noah Kennedy - An actual Tokio expert on the Pingora team
• Rain: Cancelling Async Rust - RustConf 2025 talk with many examples of pitfalls
• foundations - Cloudflare’s foundational crate for Rust project that exposes Tokio internal metrics
• io_uring - Shiny new kernel toy for async I/O
• ThePrimeTime: Cloudflare - Trie Hard - Big Savings On Cloud - “It’s not a millie, it’s not a billie, it’s a trillie”
• valuable - Invaluable crate for introspection of objects for logging and tracing
• bytes - Very foundational crate for reference counted byte buffers
• DashMap - Concurrent HashMap with as little lock contention as possible
• Prossimo - Initiative for memory safety in critical internet infrastructure
• River - Prossimo-funded reverse proxy based on Pingora
• Rustls - Memory-safe TLS implementation in Rust, also funded by Prossimo
• http crate - HTTP types for Rust
• h2 - HTTP/2 implementation in Rust
• hyper - Fast HTTP implementation for Rust
• ClickHouse Rust client - Official Rust client by Paul Loyd
• Pingap - Reverse proxy built on Pingora
• PR: Add Rustls to Pingora - by Harald Gutmann
• PR: Add s2n-tls to Pingora - by Bryan Gilbert

Official Links

• Cloudflare
• Cloudflare Blog
• Pingora on GitHub
• Edward Wang’s Blog Posts
• Kevin Guthrie’s Blog Posts

Building autonomous robots that operate safely in the real world is one of the most challenging engineering problems today. When those robots carry sharp blades and work around people, the margin for error is razor-thin.

In this episode, we talk to Andrew Tinka from Scythe Robotics about how they use Rust to build autonomous electric mowers for commercial landscaping. We discuss the unique challenges of robotics software, why Rust is an ideal choice for cutting-edge safety-critical systems, and what it takes to keep autonomous machines running smoothly in the field.
About Scythe Robotics
Scythe Robotics is building autonomous electric mowers for commercial landscaping. Their machines combine advanced sensors, computer vision, and sophisticated path planning to autonomously trim large outdoor spaces while ensuring safety around people and obstacles. By leveraging Rust throughout their software stack, Scythe achieves the reliability and safety guarantees required for autonomous systems breaking new ground in uncontrolled environments. The company is headquartered in Colorado and is reshaping how commercial properties are maintained.
About Andrew Tinka
Andrew is the Director of Software Engineering at Scythe Robotics, where he drives the development of autonomous systems that power their robotic mowers. He specializes in planning and control for large fleets of mobile robots, with over a decade of experience in multi-agent planning technologies that helped pave the way at Amazon Robotics. Andrew has cultivated deep expertise in building safety-critical software for real-world robotics applications and is passionate about using Rust to create reliable, performant systems. His work covers everything from low-level embedded systems to high-level planning algorithms.
Links From The Episode

• Ski trails rating - A difficulty rating system common in Colorado
• NVIDIA Jetson - Combined ARM CPU with a GPU for AI workloads at the heart of every Scythe robot
• The Rust Book: Variables and Mutability - Immutability is the default in Rust
• Jon Gjengset: Sguaba - A type safe spatial maths library
• The Rust Book: Inheritance as a Type System and as Code Sharing - Unlike Java, Rust doesn't have inheritance
• Using {..Default::default} when creating structs - The alternative is to initialize each field explicitly
• The Rust Book: Refutability - Rust tells you when you forgot something
• Clippy - Rust's official linter
• Deterministic fleet management for autonomous mobile robots using Rust - Andy Brinkmeyer from Arculus - 2024 Oxidize warehouse robot talk with deterministic testing
• ROS - The Robot Operating System
• Ractor - A good modern actor framework
• Rain: Cancelling Async Rust - RustConf 2025 talk with many examples of pitfalls

Official Links

• Scythe Robotics
• Scythe on LinkedIn
• Scythe on GitHub
• Andrew Tinka on LinkedIn

Are you one of over 240 million subscribers of Amazon's Prime Video service? If so, you might be surprised to learn that much of the infrastructure behind Prime Video is built using Rust. They use a single codebase for media players, game consoles, and tablets. In this episode, we sit down with Alexandru Ene, a Principal Engineer at Amazon, to discuss how Rust is used at Prime Video, the challenges they face in building a global streaming service, and the benefits of using Rust for their backend systems.

About Prime Video
Prime Video is a streaming service offered by Amazon that provides a wide range of movies, TV shows, and original content to its subscribers. With over 240 million subscribers worldwide, Prime Video is one of the largest streaming platforms in the world. In addition to its vast content library, Prime Video also offers features such as offline viewing, 4K streaming, and support for multiple devices. On the backend, Prime Video relies on a variety of technologies to deliver its content, including Rust, which is used for building high-performance and reliable systems that can handle the demands of a global audience.
About Alexandru Ene
Alexandru worked on the transition of Prime Video's user interface from JavaScript to Rust. He has been with Amazon for over 8 years and previously worked at companies like Ubisoft and EA. He has a background in computer science and is an active open source maintainer. Alexandru lives in London.
Links From The Episode

• Ferris Makes Emulators Ep.001 - The Journey Begins - First episode of a famous series where Jake Taylor wrote a Nintendo 64 emulator in Rust from scratch
• CMake - Very common build system used in C++ applications
• Conan - C++ Package Manager community project
• C++ Smart Pointers - Still a footgun
• Herb Sutter: The Free Lunch Is Over - The seminal 2005 paper that highlights the importance of concurrency, well past C++'s mainstream adoption
• Rust in Production: cURL - Baseline library used everywhere, written in C, but performant and safe
• Prime Video Platforms - One app runs on all of these
• WebAssembly (WASM) - Enabling Rust code with good performance that you can still download and run like JavaScript, avoiding the need for firmware updates on some devices
• Entity Component System - Used in the UI Rust code for pages in the app
• Bevy - Game engine written in Rust
• Leptos - UI framework that makes reactive programming in Rust easier
• tokio - The de facto standard async runtime for Rust
• SIMD - A nice feature set some CPUs support
• WebAssembly Micro Runtime - A tiny WASM runtime well suited for IoT platforms
• WebAssembly Working Group

Official Links

• Amazon Prime Video
• Rust & WASM for UI: Faster Prime Video on ANY Device - Alexandru Ene, QCon San Francisco 2024
• Alexandru Ene on LinkedIn
• Alexandru's Blog
• Alexandru Ene on GitHub

It’s time for another recap including our highlights of Season 4.

We’ve been at this for a while now (four seasons, and 32 episodes to be exact). We had guests from a wide range of industries: from Microsoft to Astral, and from password managers to satellite systems.

This time, it’s all about using Rust for foundational software, which is software that is critical to a team or even an entire organization. Rust is a great fit for this type of software!
We’ll take a break for the summer. In the meantime, we encourage you to catch up on any episodes you might have missed, and to check out the links below.

And if you’re interested in using Rust for your own projects, check out our dedicated learn page for additional content about Rust adoption or reach out to us directly for a chat.
Links From The Episode

• 10 Years of Stable Rust: An Infrastructure Story - Graydon Hoare’s reflection on Rust’s 10th anniversary
• Rust For Foundational Software - Matthias’ blog post on Rust’s role in foundational software

About Us

• Simon Brüggen (M3t0r) on GitHub
• Simon Brüggen (M3t0r) on Mastodon
• Matthias Endler on Mastodon
• About corrode Rust Consulting
• ‘Rust in Production’ Podcast on Apple
• ‘Rust in Production’ Podcast on Spotify

All Episodes of Season 4

If you missed any of the previous episodes, now is a great time to catch up:

• Episode 1: Microsoft with Victor Ciura
• Episode 2: Svix with Tom Hacohen
• Episode 3: Astral with Charlie Marsh
• Episode 4: Rust with Niko Matsakis
• Episode 5: Tembo with Adam Hendel
• Episode 6: 1Password with Andrew Burkhart
• Episode 7: KSAT with Vegard Sandengen

Credits
Podcast production by Simon Brüggen (M3t0r).
We would like to thank the guests for their time and insights. We would also like to thank you, the listener for your support and feedback. Hosting and producing a podcast is a lot of work, but it’s worth it when we hear from you. Here’s to another great season!

As a kid, I was always fascinated by space tech. That fascination has only grown as I've learned more about the engineering challenges involved in space exploration.

In this episode, we talk to Vegard Sandengen, a Rust engineer at KSAT, a company that provides ground station services for satellites. They use Rust to manage the data flow from hundreds of satellites, ensuring that data is received, processed, and stored efficiently. This data is then made available to customers around the world, enabling them to make informed decisions based on real-time satellite data.
We dive deep into the technical challenges of building reliable, high-performance systems that operate 24/7 to capture and process satellite data. Vegard shares insights into why Rust was chosen for these mission-critical systems, how they handle the massive scale of data processing, and the unique reliability requirements when dealing with space-based infrastructure.
From ground station automation to data pipeline optimization, this conversation explores how modern systems programming languages are enabling the next generation of space technology infrastructure.
About KSAT
KSAT, or Kongsberg Satellite Services, is a global leader in providing ground station services for satellites. The company slogan is "We Connect Space And Earth," and their mission-critical services are used by customers around the world to access satellite data for a wide range of applications, including weather monitoring, environmental research, and disaster response.
About Vegard Sandengen
Vegard Sandengen is a Rust engineer at KSAT, where he works on the company's data management systems. He has a Master's degree in computer science and has been working in the space industry for several years.At KSAT, Vegard focuses on building high-performance data processing pipelines that handle satellite telemetry and payload data from ground stations around the world. His work involves optimizing real-time data flows and ensuring system reliability for mission-critical space operations.
Links From The Episode

• SpaceX - Private space exploration company revolutionizing satellite launches
• CCSDS - Space data systems standardization body
• Ground Station
• Polar Orbit - Orbit with usually limited ground station visibility
• TrollSat - Remote Ground Station in Antarctica
• OpenStack - Build-your-own-cloud software stack
• RustConf 2024: K2 Space Lightning Talk - K2 Space's sponsored lightning talk, talking about 100% Rust based satellites
• K2 Space - Space company building satellites entirely in Rust
• Blue Origin - Space exploration company focused on reusable rockets
• Rocket Lab - Small satellite launch provider
• AWS Ground Station - Cloud-based satellite ground station service
• Strangler Pattern - A software design pattern to replace legacy applications step-by-step
• Rust by Example: New Type Idiom - Creating new wrapper types to leverage Rust's type system guarantees for correct code
• serde - Serialization and deserialization framework for Rust
• utoipa - OpenAPI specification generation from Rust code
• serde-json - The go-to solution for parsing JSON in Rust
• axum - Ergonomic web framework built on tokio and tower
• sqlx - Async SQL toolkit with compile-time checked queries
• rayon - Data parallelism library for Rust
• tokio - Asynchronous runtime for Rust applications
• tokio-console - Debugger for async Rust applications
• tracing - Application-level tracing framework for async-aware diagnostics
• W3C Trace Context - Standard for distributed tracing context propagation
• OpenTelemetry - Observability framework for distributed systems
• Honeycomb - Observability platform for complex distributed systems
• Azure Application Insights - Application performance monitoring service

Official Links

• KSAT
• Vegard on GitHub

Handling secrets is extremely hard. You have to keep them safe (obviously), while at the same time you need to integrate with a ton of different systems and always provide a great user-experience, because otherwise people will just find a way around your system. When talking to peers, a lot of people mention 1Password as a company that nailed this balance.
In today's episode, I talk to Andrew about how 1Password uses Rust to build critical systems that must never fail, how Rust helps them handle secrets for millions of users, and the lessons they learned when adopting Rust in their stack.
About 1Password
1Password is a password manager that helps users securely store and manage their passwords, credit card information, and other sensitive data. It provides a user-friendly interface and strong security features to protect users' secrets across multiple devices.
About Andrew Burkhart
Andrew is a Senior Rust Developer at 1Password in the Product Foundations org, on the Frameworks team and specifically on the Core Platform squad handling the asynchronous frameworks other developers use to build features (i.e. requests into the Rust core from the Native clients, data sync, etc.). He specifically specialized in that synchronization process, getting data federated from cloud to clients to native apps and back.
Links From The Episode

• Backend for Frontend Pattern - Architectural pattern for creating dedicated backends for specific frontends
• typeshare - Generate types for multiple languages from Rust code
• zeroizing-alloc - 1Password's minimal secure heap zero-on-free implementation for Rust
• arboard - Cross-platform clipboard manager written in Rust
• passkey-rs - Pure Rust implementation of the WebAuthn Passkey specification
• WebAssembly (WASM) - Binary instruction format for portable execution across platforms
• tokio - The de facto standard async runtime for Rust
• Clippy - A collection of lints to catch common mistakes in Rust
• cargo-deny - Cargo plugin for linting dependencies, licenses, and security advisories
• Nix - Purely functional package manager for reproducible builds
• Nix Flakes - Experimental feature for hermetic, reproducible Nix builds
• direnv - Load and unload environment variables based on current directory
• ACM: Spotify Guilds - A study into Spotify's Agile Model's Guilds
• axum - Ergonomic and modular web framework built on tokio and tower
• tower - Library for building robust networking clients and servers
• tracing - Application-level tracing framework for async-aware diagnostics
• rusqlite - Ergonomic wrapper for SQLite in Rust
• mockall - Powerful mock object library for Rust
• pretty_assertions - Better assertion macros with colored diff output
• neon - Library for writing native Node.js modules in Rust
• nom-supreme - Parser combinator additions and utilities for nom
• crane - Nix library for building Cargo projects
• Rust in Production: Zed - High-performance code editor built in Rust
• tokio-console - Debugger for async Rust programs using tokio
• Rust Atomics and Locks by Mara Bos - Free online book about low-level concurrency in Rust
• The Rust Programming Language (Brown University Edition) - Interactive version of the Rust Book with quizzes
• Rustlings - Small exercises to get you used to reading and writing Rust code

Official Links

• 1Password
• Andrew on GitHub
• Andrew on LinkedIn

Recently I was in need of a simple job queue for a Rust project. I already had Postgres in place and wondered if I could reuse it for this purpose. I found Tembo, a simple job queue written in Rust that uses Postgres as a backend. It fit the bill perfectly.

In today's episode, I talk to Adam Hendel, the founding engineer of Tembo, about their project, PGMQ, and how it came to be. We discuss the design decisions behind job queues, interfacing from Rust to Postgres, and the engineering decisions that went into building the extension.
It was delightful to hear that you could build all of this yourself, but that you would probably just waste your time doing so and would come up with the same design decisions as Adam and the team.
About Tembo
Tembo builds developer tools that help teams build and ship software faster. Their first product, PGMQ, was created to solve the problem of job queues in a simple and efficient way, leveraging the power of Postgres. They since made a pivot to focus on AI-driven code assistance, but PGMQ can be used independently and is available as an open-source project.
About Adam Hendel
Adam Hendel is the founding engineer at Tembo, where he has been instrumental in developing PGMQ and other tools like pg_vectorize. He has since moved on to work on his own startup, but remains involved with the PGMQ project.
Links From The Episode

• PostgreSQL - Super flexible ~40 year old relational database that just works
• R - Statistical Programming Language
• pgrx - Extend Postgres with Rust
• Postgres Docs: PL/pgSQL - Scripting with Procedural Language in PostgreSQL
• Postgres Docs: SPI - The Postgres Server Programming Interface
• pgmq - A lightweight message queue extension, initially written in Rust
• Tembo Blog: Introducing PGMQ - a blog post about the project
• sqlx - All of the great things of an ORM, without all of the bad things of an ORM
• tokio - The de facto standard async runtime for Rust
• AWS SQS - Amazon Web Services Simple Queue Service
• Postgres Docs: LISTEN - The native Postgres sub part of of pubsub
• Postgres Docs: NOTIFY - The native Postgres pub part of of pubsub
• tokio-stream - Tokio utility for asynchronous series of values
• Postgres Docs: Full Text Search - Postgres included FTS capabilities
• pgvector - The standard extension for vector/AI workloads in Postgres
• pg_vectorize - Automatically create embeddings for use with pgvector
• Python Standard Library: None - A type, but not an enum
• Rust in Production: Astral with Charlie Marsh - Massively improving Python day 1 experience
• Hugging Face candle - Use ML models in Rust

Official Links

• Tembo
• Adam on LinkedIn
• Adam on GitHub

Few developers have been as influential to my career as Niko Matsakis. Of course he is a world-class engineer with a PhD from ETH Zürich, a Rust core maintainer who has been working on the language for way more than a decade, and a Senior Principal Engineer at AWS. But more importantly, he is an empathetic human and an exceptional communicator.

I've personally been waiting for one year to get him on the show and steal one hour of his precious time. Now, finally, I got my chance at live recording at Rust Week 2025. The result is everything I hoped for: a trip down memory lane which takes us back to the early days of Rust, an honest and personal look at Rust's strengths and weaknesses, and a glimpse into the future of the language. All of that packed with insightful anecdotes based on Niko's decades of experience. If you like Rust, you will enjoy this episode.
About Rust
Rust is the language which brought us all together. What started as a side-project of Graydon Hoare, a single developer at Mozilla, has grown into a worldwide community of hobbyists, professionals, and companies which all share the same goal: to build better, safer software paired with great ergonomics and performance.
About Niko Matsakis
Niko is a long-time Rust core team member, having joined the project in 2012. He was and still is part of the team which designed and implemented Rust's borrow checker, which is the language's most important feature. He has been a voice of reason and a guiding light for many of us, including myself. His insightful talks and blog posts have helped countless developers to see the language and its goals in a new light.
Special Thanks
Thanks to RustNL, the organizers of Rust Week 2025 for inviting Simon and me to record this episode live. They did a fantastic job organizing the event, and it was an honor to be part of it.

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

• RustWeek 2025 - Rust conference in Utrecht where we recorded this live episode
• DataPower - Niko's employer before working on Rust
• XSLT - Language to transform arbitrarily shaped XML into different arbitrary shapes
• ETH Zürich - Niko's Alma Mater
• Mozilla - Niko's first employer while working on Rust
• rustboot - Rust's first compiler written in OCaml
• Don Quixote - Personification of impractical idealism, just like Rust was in the beginning
• Steve Klabnik's FOSDEM talk - Coining "The Graydon years", Slides, Recording of the same talk for ACM
• Rust 0.2 Keywords - ret for return, cont for continue
• Boxes in Rust 0.8 - ~T and @T as syntax features instead of Box and Rc
• Green Threads - Like OS threads, but greener!
• std::threads - Not green, just part of the standard library
• std::rc::Rc - The @T of std
• std::boxed::Box - The ~T of std with some special compiler sauce
• std::sync::Arc - Thread safe Rc
• pyo3::Py - A pointer type in a different library!
• The Rust Book: Understanding Ownership - Ownership and borrowing are the first third of "the simple core of Rust"
• The Rust Book: Using Trait Objects - Trait-based dispatch being the second part of "the simple core of Rust"
• std::marker::Send - A trait without even a method to dispatch, aptly placed in the marker module
• std::marker::Sync - Another example of a marker trait
• Linear Type Systems - Foundational research topic for borrowing in Rust
• regex - "Real stuff" built in Rust
• rayon - Turning iterators into parallel processing
• Tokio Async Runtime - An entire async ecosystem as a perfomant library
• Comment on RFC 2394 - The beginning of the await x / x.await discussion?
• Alex Crichton - Rust compiler, wasm, and lang-advisors team member
• cramertj - Rust lang-advisors and libs-contributors team member
• withoutboats - Rust team alumni
• Carl Lerche - tokio maintainer
• aturon - Rust team alumni
• ALGOL 60 - Doesn't look like C
• try blocks - Do we need a postfix match operator for this?
• Rust Blog: Announcing Rust 1.31 and Rust 2018 - A watershed moment for Rust
• Non-lexical lifetimes - Included in 1.31 and Rust 2018
• Santiago Pastorino - Rust compiler contributor, worked on non-lexical lifetimes
• Makefile Example - "We don't need cargo, Make is fine"
• Rust Blog: Laying the foundation for Rust's future - Mozilla's parting gift to Rust?
• Tyler Mandry - Rust lang team co-lead with Niko
• Josh Triplett - Rust lang, cargo, and libs team member
• Amazon S3 Express One Zone storage class - Super low latency S3, written in Rust
• Amazon Aurora DSQL - Serverless SQL, an AWS project that started 100% in JVM and finished 100% Rust
• Just make it scale: An Aurora DSQL story - Blog post detailing the Aurora DSQL Rust rewrite
• Rust in 2025: Targeting foundational software - Niko's vision for Rust
• Be excellent to each other - Party on dudes!

Official Links

• Rust Language
• Rust Foundation
• Niko Matsakis' Homepage
• Niko Matsakis on GitHub

Up until a few years ago, Python tooling was a nightmare: basic tasks like installing packages or managing Python versions was a pain. The tools were brittle and did not work well together.
Then, suddenly, we saw a renaissance of new ideas in the Python ecosystem. It started with Poetry and pipx and continued with tooling written in Rust like rye, which later got incorporated into Astral.Astral in particular contributed a very important piece to the puzzle: uv -- an extremely fast Python package and project manager that supersedes all previous attempts; For example, it is 10x-100x faster than pip.
In this episode I talk to Charlie Marsh, the Founder and CEO of Astral. We talk about Astral's mission and how Rust plays an important role in it.
About Astral
Astral is a company that builds tools for Python developers. What sounds simple is actually a very complex problem: Python's ecosystem is huge, but fragmented and often incompatible. Astral’s mission is to make the Python ecosystem more productive by building high-performance developer tools, starting with Ruff. In their words: "Fast, unified, futuristic."
About Charlie Marsh
Charlie is a long-time open source developer and entrepreneur. He has an impressive CV, graduating with highest honors from Princeton University. After that, he worked at Khan Academy and others before eventually founding Astral in '22. Charlie is an engaging speaker and a great communicator.

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

• ruff - Python static linter and formatter written in Rust
• uv - Python package and project manager written in Rust
• rustfmt - Rust code formatter
• clippy - Linter for Rust code
• The Rust Programming Language: Cargo Workspaces - The Rust Book's chapter on workspaces
• pip - Package Installer for Python
• pip documentation: Requirements File Format - A description of the format of requirements.txt, including a list of embedded CLI options
• uv's CI - Build scripts for many different platforms
• jemalloc - Alternative memory allocator
• zlib-ng - Next Generation zlib implementation in C
• reqwest - An easy and powerful Rust HTTP Client
• zlib-rs - Pure Rust implementation of zlib
• XCode Instruments - Native macOS performance profiler
• CodSpeed - Continuous benchmarking in CI
• hyperfine - "macro benchmarking" tool, coincidentally written in Rust
• samply - Sampling based profiler written in Rust
• cargo flamegraph - Cargo profiling plugin
• tokio - Asynchronous runtime for Rust
• curl-rust - Network API used in cargo
• tar-rs - Sync tar crate
• async-tar - Async tar crate based on the async_std runtime
• tokio-tar - Async tar crate based on tokio
• astral-tokio-tar - Async tar crate based on tokio, maintained by Astral
• RustPython - Python interpreter written in Rust
• lalrpop - The parser generator used by RustPython
• Charlie's EuroRust 2024 Talk - Mentions the version number parser at 18:45
• ripgrep - Andrew Gallant's idiomatic Rust project, which also happens to be a very fast CLI file search tool

Official Links

• Astral
• Charlie's Website
• Charlie on GitHub

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

• Microsoft IIS - Microsoft's HTTP server
• Elixir - General purpose programming language based on the Erlang VM
• Go Spec: Exported Identifiers - How to mark interface functions as public
• Bob Nystrom: What Color is Your Function? - A good explanation of colored functions and the problems they introduce
• jemallocator - Use jemalloc as the global allocator in Rust
• serde-json - The go-to solution for parsing JSON in Rust
• serde - High-level serilization and deserialization interface crate
• axum - The defacto async web server crate
• seaorm - SeaORM is a relational ORM to help you build web services in Rust
• redis-rs - Redis library for rust
• aide - OpenAPI generation from axum code
• dropshot - Oxide API framework that generates OpenAPI spec
• KSUID - A pure-Rust K sorted UID implementation
• omniqueue - A queue abstraction layer for Rust
• Python GIL - The Global Interpreter Lock Python wiki entry
• Svix Blog: Robust APIs Through OpenAPI Generation - How to build stable APIs through schema generation and reviews

Official Links

• Svix
• Tom Hacohen's Blog
• Tom on GitHub
• Tom on Mastodon