The complexity tax is the extra files, interfaces, and mapping logic required by a more decoupled architecture. You pay it for benefits such as containing changes to an external API and reusing the core through different adapters. section 5.5.4
Use the expected payoff to decide whether the tax is worth paying:
- For a simple CRUD prototype, the added structure may be overkill. section 5.5.4
- For a long-lived system with complex rules, the upfront cost may help avoid slower work as technical debt grows. section 5.5.4
- When refactoring a legacy system, count the cost before converting everything; a gradual migration can move logic into the new architecture over time. section 5.7.1
