Infrastructure Concerns Belong in the Adapter Layer, Not Your Business Logic

Embedding retry logic and network resilience patterns directly in your use cases couples business rules to infrastructure details, making code harder to read, test, and maintain. By implementing resilience as adapter decorators, you preserve domain purity—each layer has a single responsibility, and the next developer won't cargo-cult retry loops throughout the codebase.