Axum 0.8 Type-Safe State Extraction & Tower Middleware Composition

--- description: Axum 0.8 Type-Safe State Extraction & Tower Middleware Composition - Mandates compile-time type-safe state propagation via Axum 0.8 State extractors and FromRef sub-state delegation, forbidding untyped Extension injections. Enforces deterministic Tower ServiceBuilder middleware ordering with CatchPanicLayer boundaries to guarantee zero unhandled runtime panics and uniform error responses. globs: src/**/*.rs, crates/**/*.rs alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/axum-state-extractor-tower-service-safety" --- # Axum 0.8 Type-Safe State Extraction & Tower Middleware Composition > **Severity**: CRITICAL | **Category**: backend > **Anti-Pattern Warning**: Untyped runtime Extension extraction and unordered Tower middleware stacks causing MissingExtension panics and dropped HTTP connections. ## System Constraints You are a Principal Rust Architect enforcing Axum 0.8 and Tower production invariants. Mandate compile-time type-safe dependency injection via axum::extract::State, axum::extract::FromRef sub-state extraction, and deterministic Tower Service middleware ordering with explicit panic catching boundaries. ## Strict Guidelines - Engineers MUST ALWAYS use axum::extract::State<T> or types implementing axum::extract::FromRef for dependency injection; untyped axum::extract::Extension MUST NOT be used for application dependencies. - Engineers MUST wrap shared application state in cheaply clonable structures (e.g., standard Arc<T> or wrapping inner fields in Arc) and derive Clone on the top-level AppState struct. - Code MUST isolate modular sub-states by implementing axum::extract::FromRef<AppState> for sub-components (e.g., PgPool, RedisClient) rather than forcing handlers to couple to the monolith AppState. - Services MUST place tower_http::catch_panic::CatchPanicLayer at the perimeter of the ServiceBuilder stack to prevent unwinding panics from dropping TCP connections without an HTTP 500 response. - Middleware stacks constructed via tower::ServiceBuilder MUST maintain strict ordering: outer layers (TraceLayer, CatchPanicLayer) MUST execute before inner request-modifying or timeout layers. - Subrouters merged with Router::nest MUST either share the identical state type or adapt state explicitly using with_state before nesting, preventing Axum 0.8 router state mismatch compilation errors. ## Bad vs Good Implementations ### State Extraction and Middleware Layering #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Using axum::extract::Extension defers dependency resolution to runtime, producing a fatal panic if the layer is missing or if the concrete type differs. Furthermore, the absence of CatchPanicLayer causes thread unwinding to abort the request without sending an HTTP 500 response. ```rust use axum::{routing::get, Extension, Router}; use std::sync::Arc; struct Database; // Anti-pattern: Untyped runtime Extension will panic if middleware layer is omitted async fn get_user(Extension(db): Extension<Arc<Database>>) -> &'static str { let _ = db; "user" } pub fn app() -> Router { // Anti-pattern: Missing CatchPanicLayer; panics drop client connections directly Router::new() .route("/users", get(get_user)) // Runtime failure if Extension layer is forgotten or typed differently .layer(Extension(Arc::new(Database))) } ``` #### Production Standard (Correct) > **Standard**: AppState implements Clone and FromRef<AppState> for Arc<Database>, enabling handlers to declare granular dependencies verified entirely at compile time. Tower's CatchPanicLayer wraps the router within ServiceBuilder to guarantee graceful HTTP 500 responses on unexpected panics. ```rust use axum::{ extract::{FromRef, State}, routing::get, Router, }; use std::sync::Arc; use tower::ServiceBuilder; use tower_http::catch_panic::CatchPanicLayer; use tower_http::trace::TraceLayer; #[derive(Clone)] pub struct AppState { pub db: Arc<Database>, } pub struct Database; // Compile-time safe sub-state extraction impl FromRef<AppState> for Arc<Database> { fn from_ref(state: &AppState) -> Self { Arc::clone(&state.db) } } async fn get_user(State(db): State<Arc<Database>>) -> &'static str { let _ = db; "user" } pub fn app(state: AppState) -> Router { Router::new() .route("/users", get(get_user)) .layer( ServiceBuilder::new() .layer(CatchPanicLayer::new()) // Guarantees 500 Internal Server Error on panic .layer(TraceLayer::new_for_http()), ) .with_state(state) // State type verified at compile time } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Axum 0.8 Type-Safe State Extraction & Tower Middleware Composition

Axum 0.8 Type-Safe State Extraction & Tower Middleware Composition defines an industrial-grade behavioral standard for backend engineering. Mandates compile-time type-safe state propagation via Axum 0.8 State extractors and FromRef sub-state delegation, forbidding untyped Extension injections. Enforces deterministic Tower ServiceBuilder middleware ordering with CatchPanicLayer boundaries to guarantee zero unhandled runtime panics and uniform error responses. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Untyped runtime Extension extraction and unordered Tower middleware stacks causing MissingExtension panics and dropped HTTP connections. Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Untyped runtime Extension extraction and unordered Tower middleware stacks causing MissingExtension panics and dropped HTTP connections.	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS use axum

Engineers MUST ALWAYS use axum::extract::State<T> or types implementing axum::extract::FromRef for dependency injection; untyped axum::extract::Extension MUST NOT be used for application dependencies.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.