m13-domain-error

Design a domain error framework by classifying errors into a taxonomy of User-facing, Internal, System, Transient, and Permanent types, then prescribing targeted recovery strategies like retry with backoff, fallbacks, and circuit breakers for each category.

Handle transient errors by implementing recovery strategies like retry with backoff, fallbacks, timeouts, and circuit breakers to prevent cascading failures and ensure API resilience during temporary system disruptions.

A circuit breaker fits into error categorization as a recovery strategy for transient and system errors, stopping cascading failures by tripping after repeated failures, while allowing trace-up and trace-down relationships for observable diagnostics.

Yes, this domain error framework applies to microservices and asynchronous workflows requiring structured error handling, clear user-facing versus internal typing, context propagation, and observable tracing to support debugging.

Distinguish between user-facing and internal error types across synchronous and asynchronous workflows to ensure clear communication, prescribing appropriate recovery strategies and context propagation for observable diagnostics.

Your strategy may lack observable tracing and context propagation. A robust domain error framework requires explicit error categorization, trace-up and trace-down relationships, and prescribed recovery strategies to support debugging and resilience.