u/Crazy_Fireflyin r/rust • Recommends
On “Super heavy generic on HTTP lib makes debugging hard”
Advanced. Deep dive for people who know the field.
103K views3 years ago5 recommendations
Web developmentProgramming languagesRustHTTP, REST and GraphQLFull-stack frameworks
Jon Gjengset explores the internals of the axum web framework, explaining tower services, handlers, and state extractors.
In this stream, we peel back the crust on the axum crate — github.com/tokio-rs/axum/ — and explore its interface, structure, and mechanisms. We talk about tower::Service, the Handler trait, Routers, and the State extractor. We also get into the way axum ensures at compile time that all handlers have access to the state that they'll need at runtime. For more details about axum, see docs.rs/axum/latest/axum/. Introduction axum tower::Service The Handler trait and its impls The State extractor axum's use of other crates Unstable features axum wants State requiring that T: CLone FromRef Handling custom HTTP methods axum_extra Live version with chat (part 1): youtube.com/live/ntqGaoEFYiQ?feature=share Live version with chat (part 2): youtube.com/live/36m4dxJ0AHg?feature=shareWhat people say. Highly recommended for understanding how Axum works at a deep level, especially its complex generic handler system.
u/Crazy_Fireflyin r/rust • Recommends
On “Super heavy generic on HTTP lib makes debugging hard”
u/fryuniin r/rust • Recommends
On “Is anyone actually productive in the Axum/Tower ecosystem?”
u/ToTheBatmobileGuyin r/rust • Recommends
On “How does an Axum handler work at the language level?”
u/coolstorm1820in r/rust • Recommends
On “How to go from Zero to Rust backend developer?”
u/cornell_cubesin r/rust • Recommends
On “Preparing for Rust (Axum) Backend Interviews — Need Guidance”