m13-domain-error

Design a domain error handling strategy by categorizing errors based on audience and recovery potential, then defining specific recovery patterns like retry with backoff or circuit breakers to maintain system resilience.

Categorize transient and permanent errors by evaluating their recovery potential and audience, differentiating between user-facing, internal, and system errors to determine appropriate recovery strategies and user-facing messages.

Use retry with backoff or circuit breaker patterns during error recovery when handling transient service unavailability, ensuring the system can gracefully recover from temporary failures without cascading downtime.

Ensure domain errors provide adequate context by designing audience-specific recovery and implementation tracing, addressing requirements for user-facing messages alongside internal debugging context to clarify who handles the error.

Yes, you can apply this error categorization approach to network timeouts and database connection failures by classifying them as transient errors and mapping them to appropriate recovery strategies like retry or fallback to maintain resilience.