Translate Infrastructure Errors at the Adapter, Not in Your Domain

In Decoupled PHP and Thinking in Go, the author emphasizes that infrastructure errors and retry logic must reside in the adapter rather than the domain or use case. Examples include translating SQLSTATE integrity constraint violations and managing flaky payment gateways. Moving retry loops and exception handling out of the application layer prevents domain pollution, ensuring that use cases remain clean and focused on business logic while adapters manage technical failures and external system instabilities.