1. Clean Architecture intermediate Multiple choice

    A service calls a payment provider over HTTP. The provider occasionally returns 503 and occasionally times out. In a domain / application / adapter layering, which layer should own the retry and backoff policy?

    3 min answer clean architecturehexagonalretrieslayering
  2. Clean Architecture intermediate

    A team adopts a layered architecture with strict dependency rules and finds every small change touches many files. Is the architecture wrong, or the application of it?

    2 min answer clean-architecturelayersindirectionpragmatism
  3. Clean Architecture advanced

    A use case renders a basket of up to 200 lines. It calls a repository port's findById once per line. In the domain layer this looks like a clean loop with no infrastructure knowledge, and p99 has climbed to 2.4 s. The dependency rule forbids the domain from knowing about SQL. What do you change?

    3 min answer clean-architectureports-and-adaptersn-plus-onequery-shape
  4. Clean Architecture intermediate

    Review this design. Every repository method opens its own transaction and commits before returning. One use case calls four repositories and then publishes an event. Support reports occasional orders with a payment row and no shipment row. What would you change and what would you leave alone?

    3 min answer clean architectureunit of worktransactionsoutbox
  5. Clean Architecture advanced

    When is clean architecture over-engineering, and what is the signal that you have its costs without its benefits?

    2 min answer clean-architectureanaemic-domainover-engineeringcost