sfermanelli-error-handling

What problem does it solve?

Design error handling that makes failures visible, recoverable, and debuggable. Errors are not exceptional — they are expected. A system that handles errors well is more valuable than one that never errors in testing.

Core Features & Use Cases

• Error hierarchies separate domain, application, and infrastructure errors to clarify responsibility and enable targeted handling.
• Error boundaries, retries, and graceful degradation to isolate failures, recover from transient issues, and preserve service availability.
• Logging and HTTP error handling to present actionable, safe error responses while supporting observability across services.
• Use Case: when a downstream service fails transiently, apply retry, circuit breaker, and structured error signaling to minimize user impact.

Quick Start

Start by defining a layered error hierarchy (DomainError, ValidationError, InfrastructureError) and wire a centralized error handler that logs, formats responses, and gracefully degrades when external services fail.