This technical talk examines the most prevalent pain points facing Rust web developers today and explores how the community is addressing them.


The Rust web ecosystem has made incredible progress, but let's talk about what we don't discuss enough: the rough edges. Every web developer working in Rust has battled macro-heavy frameworks that obscure what's actually happening, ORM integration headaches that turn simple queries into type gymnastics, and error handling that makes it hard to return clean, user-friendly error messages instead of exposing internal implementation details.
This technical talk examines the most prevalent pain points facing Rust web developers today and explores how the community is addressing them. We'll discuss common developer frustrations, emerging patterns and solutions, and honest assessments of what's improving versus what remains challenging. Whether you're shipping production Rust backends or evaluating the ecosystem, you'll walk away with a clearer picture of the real-world challenges and where the community is headed.
In this talk, we'll dive deep into what makes concurrency coordination costly, and explore some pathways to mitigate that cost.
In my session, I will present the https://hotpath.rs crate and explain how it compares to other profiling tools available.
For infrastructure engineers, SREs, platform teams, and Rust developers who've felt the pain of configuration drift, failed deployments, and infrastructure code that simply doesn't scale safely.
The talk explores how Rust’s type system and memory safety can be leveraged to enforce mandatory guardrails at the infrastructure level, where traditional frameworks often fall short.