Building composable web services with Axum
summary
A compact walkthrough of using Axum, Tower and Rust types to keep a growing web service modular: a cat‑daycare example shows Axum extractors as DI with handlers depending on explicit types, traits for swappable storage so tests use an in‑memory Vec while prod uses a DB adapter, and Tower middleware for logging/auth/rate limits to keep concerns out of domain code. Advice includes cargo workspaces to split crates, typed config per state, tracing for observability, and incremental refactor steps that actually work.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 3:39Cat daycare setup
- 6:29Architecture matters
- 8:16Composable service boundaries
- 13:13Rust and Axum tools
- 16:52Extractors and handlers
- 17:35Middleware with Tower
- 18:40Workspaces for scaling
- 19:45Stable API contracts
- 22:36Database integration
- 23:40Observability in Axum
- 24:46Refactoring messy services
- 26:31Cat daycare evolution
- 28:16Key takeaways
- 30:12Q&A
related talks
28mRust Irgendwie, Irgendwo, Irgendwann
01h 13mRust-Powered Fullstack GraphQL: From Actix-Web & Juniper Server to WASM Yew Client
39mRefactoring in Rust
36mWeb development with Rust, is it ready? Is it even useful?
42mBuilding a Web Application with Rust
23mRust's Module System For Effective Software Architecture
59mWrite HTTP APIs
27mThe State of Rust Web Frameworks: Pros, Cons & Use Cases