m13-domain-error

Domain error categorization classifies errors into user-facing, internal, system, transient, and permanent types to balance user experience, debugging, and resilience. It guides recovery policies by distinguishing recoverable transient failures from permanent system faults.

Design a retry strategy by applying backoff patterns, fallback defaults, and circuit breakers to handle transient errors. In Rust, map these design decisions to concrete code using crates like thiserror, anyhow, and dedicated retry libraries for resilient execution.

The best way to structure error handling for a payment service is defining domain error categories, recovery strategies, and contextual error information. This includes retry policies, user-facing messages, and compliance logging to ensure robust transaction processing.

Use circuit breaker patterns instead of simple retries when system errors indicate sustained downstream failures. Categorize errors as transient or permanent first; apply retry with backoff for transient issues, but trigger circuit breakers to prevent cascading system failures.

Yes, this approach works with Rust crates like thiserror and anyhow. It provides implementation guidance that maps domain error categorization and recovery strategies directly to concrete code examples using these libraries and retry mechanisms.

Add contextual information to domain errors by defining context-aware error types across user-facing, internal, and system categories. This systematic approach ensures errors carry sufficient debugging context while maintaining appropriate user-facing messages and recovery policies.