liveBook · Manning

Complexity tax

As explained in Grokking Software Architecture

The additional implementation complexity and maintenance burden incurred by adopting a more decoupled architectural structure.

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

How Grokking Software Architecture covers it

How deep it goes
Defines the costs and tradeoffs, but does not quantify them.
Examples
Contrasts a simple CRUD prototype with a long-lived system containing complex rules, and considers legacy refactoring.
What you can do after
Evaluate whether added architectural structure is justified by a system’s expected lifespan, rule complexity, and maintenance needs.
How it connects
Connects Hexagonal Architecture with Active Record, Layered Architecture, adapters, and technical debt.

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.