crud-handler-http

To separate HTTP request validation from business logic, bind and validate DTOs directly in the HTTP handler, then delegate processing to the service layer. This ensures handlers avoid DB or IO operations, maintaining strict separation of concerns.

Standardize REST API error handling by using a unified response and error bridge across endpoints. This approach maintains consistent REST contracts by mapping service layer errors to standardized HTTP responses.

Structure multi-tenant API routes by registering them in api.go with a /api/v1/admin|open|web prefix. Multi-tenant context is then supported through middleware, ensuring proper isolation and consistent pagination across requests.

Yes, you can use dependency injection via *shared.Deps to provide necessary dependencies to HTTP handlers. This prevents handlers from directly accessing the DB or performing IO, keeping them focused on binding and validation.

HTTP handlers should avoid database and IO operations to enforce strict separation of concerns. Keeping handlers limited to binding, validation, and delegation ensures business logic remains testable and isolated in the service layer.

You need DTO binding in HTTP handlers when you want to validate incoming requests at the transport layer before passing them to the service layer. This ensures only properly formatted and validated data reaches your business logic.