error-handling

Standardize .NET error handling by implementing a DomainException base class and mapping it to ProblemDetails for REST and RpcException for gRPC. This unifies responses through centralized status-code mapping and structured logging across both protocols.

The best way to map domain exceptions to gRPC RpcException is using an ApplicationExceptionInterceptor. This interceptor catches domain exceptions, sets the correct gRPC StatusCode, and attaches problem-details-bin metadata for client-friendly responses.

ProblemDetails works with custom domain exceptions by implementing an IProblemDetailsProvider interface. This allows exceptions like NotFoundException or ValidationException to generate rich REST error responses containing Type, Title, Status, and Detail fields.

Yes, structured logging captures contextual properties like ErrorCode, Entity names, and identifiers during exception handling. This enables effective traceability by appending these details to logs when domain exceptions are thrown and processed.

Common error handling anti-patterns include throwing generic, uninformative exceptions without specific domain context or structured logging. This prevents clients from understanding failures and hinders debugging due to missing error codes and mapped status details.

Yes, using separate exception types like ValidationException and ConcurrencyException within a DomainException hierarchy expresses precise failure modes. This allows distinct status-code mapping and accurate ProblemDetails generation for each specific error.