error-handling

Layered exception handling assigns distinct responsibilities for managing errors across infrastructure, service, and API/CLI layers. This approach translates low-level exceptions into domain-specific errors at layer boundaries to ensure resilience and maintainability throughout the application architecture.

Implementing safe retry logic requires using an exponential backoff pattern for transient failures. This strategy ensures graceful degradation and maintains functionality when external services or infrastructure components temporarily fail, preventing cascading application crashes.

Exception mapping translates low-level infrastructure exceptions into domain-specific errors at layer boundaries. For example, a database connection error caught by the repository layer becomes a ServiceUnavailable domain error, which the API layer then maps to a 503 HTTP response.

Common error handling anti-patterns include failing to preserve tracebacks during logging and skipping exception translation at layer boundaries. Addressing these ensures robust error management by maintaining clear exception context and achieving graceful degradation across application layers.

Yes, this error handling strategy defines distinct responsibilities for both API and CLI layers. It ensures robust error management by translating domain errors into appropriate API HTTP responses or CLI exit codes while logging the original error with its traceback.

Logging exceptions incorrectly often causes the original traceback to be lost. Following correct logging best practices preserves tracebacks by capturing the original error context before translating it into domain-specific errors at application layer boundaries.