{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Which Rust web framework is built directly on tokio and tower, favoring a modular trait-based approach?","acceptedAnswer":{"@type":"Answer","text":"Axum is built on tokio and tower, using tower's Service and Layer system for middleware. This architecture enables great composability and natural integration with the tower ecosystem (timeout, rate limiting, tracing). Axum leverages Rust traits for data extraction and type-safe handler management."}},{"@type":"Question","name":"How to define a GET route with a path parameter in Axum?","acceptedAnswer":{"@type":"Answer","text":"In Axum, path parameters use the :param syntax in route definition, and are extracted via the Path extractor. Type T must implement Deserialize, enabling type-safe extraction. The order of extractors in the handler signature determines how data is extracted from the request."}},{"@type":"Question","name":"What is the distinctive feature of Actix-web's execution model compared to other Rust frameworks?","acceptedAnswer":{"@type":"Answer","text":"Actix-web uses the actor model where each worker is an independent actor with its own state. Requests are handled by actors communicating via asynchronous messages. This model provides excellent isolation and natural horizontal scalability, though the actor model is no longer mandatory in recent versions."}},{"@type":"Question","name":"How to share application state between handlers in Axum?","acceptedAnswer":{"@type":"Answer","text":"In Axum, application state is shared via Extension or State. State is preferred as it's typed and extracted directly from the Router. The type must be Clone since state is cloned for each request. For shared mutable state, using Arc> or Arc> enables safe concurrent access."}},{"@type":"Question","name":"What is Rocket's syntax for defining a route with automatic JSON body validation?","acceptedAnswer":{"@type":"Answer","text":"Rocket uses procedural attributes like #[post] with the Json type for automatic deserialization. Type T must derive Deserialize. Rocket performs validation and returns a 400 error if deserialization fails. This declarative approach makes code very readable and reduces boilerplate."}},{"@type":"Question","name":"How to implement a logging middleware in Axum using tower?","acceptedAnswer":{"@type":"Answer","text":"Axum uses tower's Layer system for middleware. TraceLayer from tower-http provides comprehensive HTTP logging with tracing spans. Layers are applied via the Router's layer() method and execute in reverse order of addition (last added executes first for incoming requests)."}},{"@type":"Question","name":"What is the main difference between an Extractor and FromRequest in Axum?","acceptedAnswer":{"@type":"Answer","text":"FromRequest and FromRequestParts are the traits that define extractors in Axum. FromRequestParts extracts data without consuming the body (headers, path params), while FromRequest can consume the entire body. Extractors that consume the body must be the last handler arguments since the body can only be read once."}},{"@type":"Question","name":"How does Actix-web handle sharing mutable state between concurrent requests?","acceptedAnswer":{"@type":"Answer","text":"Actix-web uses web::Data for state sharing. For mutable state, T is typically Arc> or Arc>. web::Data is cloned for each request, but the underlying Arc points to the same data. RwLock is preferred for frequent reads as it allows multiple simultaneous readers."}},{"@type":"Question","name":"What is Rocket's main advantage regarding request error handling?","acceptedAnswer":{"@type":"Answer","text":"Rocket uses Catchers to handle HTTP errors centrally. Catchers are defined with #[catch(code)] and allow customizing responses for each error code. Rocket also provides rich error types that integrate with Rust's type system for compile-time error handling."}},{"@type":"Question","name":"How to define a route group with a common prefix in Axum?","acceptedAnswer":{"@type":"Answer","text":"Axum uses the nest() method to create sub-routers with a prefix. The nested Router inherits parent state if compatible. This approach enables modular code organization and facilitates applying specific middleware to a route group via layer() on the sub-router."}},{"@type":"Question","name":"What approach does Actix-web use for route configuration via macros?","acceptedAnswer":{"@type":"Answer","text":"Actix-web provides attribute macros like #[get], #[post], etc. that annotate handlers. These macros generate routing code at compile time. Decorated routes are then registered via App::new().service(handler). This approach combines declarative readability with generated code performance."}},{"@type":"Question","name":"How to return a JSON response with a custom status code in Axum?","acceptedAnswer":{"@type":"Answer","text":"Axum allows combining StatusCode with Json in a tuple to customize responses. Tuples (StatusCode, Json) implement IntoResponse. This approach is composable: headers can be added via (StatusCode, [(HeaderName, HeaderValue)], Json) for full response control."}},{"@type":"Question","name":"How does Rocket handle fairings (middleware) compared to tower in Axum?","acceptedAnswer":{"@type":"Answer","text":"Rocket uses Fairings which are callbacks for different lifecycle phases (launch, request, response). Unlike tower layers that wrap services, fairings are event hooks. Fairings can modify requests/responses or perform actions at specific moments like server startup."}},{"@type":"Question","name":"What is the correct way to extract query parameters in Actix-web?","acceptedAnswer":{"@type":"Answer","text":"Actix-web uses web::Query to extract query parameters. Type T must implement serde's Deserialize. Parameters are automatically deserialized from the query string. If parameters are optional, use Option for fields or Query> for the entire extractor."}},{"@type":"Question","name":"How to implement authentication middleware in Axum with custom rejection?","acceptedAnswer":{"@type":"Answer","text":"The recommended approach is creating a custom extractor implementing FromRequestParts. The extractor verifies the token in headers and returns either the authenticated user or a custom error type implementing IntoResponse. This type-safe approach guarantees protected routes always receive a valid user."}},{"@type":"Question","name":"What is the difference between web::Path and web::Data in Actix-web?","acceptedAnswer":{"@type":"Answer","text":"web::Path extracts URL parameters (e.g., /users/{id}), while web::Data extracts shared application state configured during app setup. Path is specific to each request based on URL, Data is application-global and shared across all requests."}},{"@type":"Question","name":"How does Axum handle routes with multiple HTTP methods on the same path?","acceptedAnswer":{"@type":"Answer","text":"Axum uses MethodRouter to combine multiple methods on the same path. Methods can be chained with .get(handler1).post(handler2) or use method_router::on() for custom methods. This approach avoids path duplication and logically groups handlers for the same resource."}},{"@type":"Question","name":"How to handle multipart/form-data requests for file uploads in Actix-web?","acceptedAnswer":{"@type":"Answer","text":"Actix-web uses actix-multipart to handle uploads. Multipart is a stream of Fields representing each form part. Files are read progressively to avoid loading everything in memory. Configuring size limits is important to prevent denial of service attacks."}},{"@type":"Question","name":"What is the best practice for configuring CORS in Axum?","acceptedAnswer":{"@type":"Answer","text":"Axum uses tower-http::cors::CorsLayer for CORS configuration. This tower layer is added via .layer() and allows configuring allowed origins, methods, headers and credentials. CorsLayer should generally be added last to execute first on incoming requests."}},{"@type":"Question","name":"How to define an Axum handler that returns different response types based on conditions?","acceptedAnswer":{"@type":"Answer","text":"Axum offers several options: using impl IntoResponse as return type allows returning any type implementing this trait. For explicitly different types, Response or axum::response::Response unifies responses. Custom enums implementing IntoResponse offer the best typing."}},{"@type":"Question","name":"What approach to use for WebSockets in Axum?","acceptedAnswer":{"@type":"Answer","text":"Axum provides WebSocketUpgrade as an extractor that enables upgrading an HTTP connection to WebSocket. The on_upgrade() method takes an async closure that receives the WebSocket and handles bidirectional communication. tokio-tungstenite is used under the hood for the WebSocket protocol."}},{"@type":"Question","name":"How to structure a production Axum application with separation of concerns?","acceptedAnswer":{"@type":"Answer","text":"A recommended architecture separates routes (endpoint definitions), handlers (HTTP logic), services (business logic) and repositories (data access). Handlers stay thin and delegate to services. Application state (DB pool, config) is injected via State. Modules organize code by functional domain."}}]}