rust-patterns

Standardize Rust error handling by using thiserror for library-level errors and anyhow for application-level errors. This separation provides precise error mapping for HTTP responses while maintaining flexible error context propagation in application code.

Structure database access patterns in sqlx by defining repository methods within dedicated repository modules. This approach encapsulates transaction examples and typical query patterns, ensuring consistent data access logic across your Rust project.

Use PascalCase for Entities, suffix DTOs with their purpose, and append Repository or Service to those respective structs. Handlers should use verb prefixes, and errors must end with Error to maintain clear Rust code conventions.

Yes, these Rust coding conventions recommend using axum alongside sqlx, serde, and tokio. The guidelines include mapping application errors to HTTP responses, ensuring your axum web services follow standardized error handling and data access patterns.

Scaffold a new Rust feature by defining entities, creating corresponding repositories for sqlx data access, and implementing services for business logic. Apply standard naming and use thiserror or anyhow for consistent error handling throughout the module.