I dodged axum for a year, sure a Rust web framework would fight me on every handler. It didn't. Here's the axum setup, state, and…
Rust vs Go, decided by what you are building rather than benchmarks: where the borrow checker pays off, where Go's compile times win, and when…
I avoided Rust macros for a year, then learned them in a weekend. Here is when macro_rules! earns its place, when to skip proc macros,…
Two years, three runtimes, one grumpy migration weekend. Here is the Rust async runtime I ship with in 2026, and the cancellation trap that cost…
After two years of running Diesel and sqlx in Rust production services, here is how I actually pick between them in 2026, and what each…
I picked axum for a Rust service and spent a weekend on basics nobody documents. Here's the axum + sqlx production setup I actually ship,…
How I actually choose a Rust web framework in 2026, with the four questions I ask before opening Cargo.toml and a real code snippet from…
I've shipped production services in both Rust and Go. Here's the decision framework I actually use, with code, honest trade-offs, and no benchmark wars.
How I split thiserror and anyhow inside Axum handlers, then let IntoResponse map domain errors to real status codes without leaking internals to callers.
The Axum patterns I actually use in production Rust services: extractors, Tower layer ordering, an error enum that works, and pragmatic tracing.