Rust Web Services

Use this when request lifecycle, service state, and failure reporting shape the Rust design.

Working stance

• Keep handlers thin; move business rules behind service boundaries.
• Parse and validate at the edge, then hand typed data inward.
• Shared state should have a clear owner and a narrow mutation story.
• Timeouts, backpressure, and shutdown are part of correctness.
• Pair this skill with rust-async-and-concurrency or rust-errors, not both by default.

Domain pressure