liveBook · Manning

Overengineering

As explained in Software Architecture Decision-Making

Overengineering is adding design complexity or capability beyond what current evidence and requirements justify.

Overengineering adds complexity for a future that current evidence does not yet justify. It commonly appears when extensibility, scale, resilience, or idealized design are treated as immediate requirements despite costs in delay, operational burden, and team cognitive load. Foresight remains necessary; the mistake is paying now for every problem that might occur. section 1.1 section 3.7

The alternative is not careless simplification. Good-enough architecture balances correctness, security, operability, understandability, recoverability, time, cost, team capability, ownership, and risk. Give added complexity a clear present reason, apply more care to expensive-to-reverse decisions, and keep uncertain decisions cheap to change. section 3.2 section 3.7

Useful signals that a design may be overengineered include:

  • Complexity justified mainly by hypothetical demand, integrations, or organizational needs. section 3.2
  • Patterns or operational responsibilities that the team cannot sustain. section 3.7
  • Heavy investment in functionality that is temporary, experimental, tactical, or low-value. section 3.2
  • Redesign triggered by every signal rather than by evidence of urgency or value. section 1.1

Start lighter, retain a response path

A reporting capability constrained by a fixed date, small team, modest usage, limited operational capacity, and no real-time requirement need not begin as several services with an event stream. A lighter design can be revisited as production feedback changes the constraints. Likewise, a system need not be built for massive scale on day one, but it needs a feasible way to respond if demand arrives faster than expected. section 1.1 section 4.1

Figure 1.1 Architecture as a feedback loop. Intent is shaped by forces, translated into decisions, and tested through consequences, feedback, and adaptation.

Use the feedback loop to separate decisions that require action now from concerns worth documenting, watching, and revisiting at later review points. section 1.1

Treat architecture as a continuing economic and operational judgment. Watch consequences such as saturation, rising error rates, increasing manual work, and exceeded scaling assumptions. Strengthen or redesign when evidence warrants it, especially where security, data integrity, compliance, or mission-critical resilience leave little room for compromise. A durable heuristic is to decide at the last responsible moment: late enough to learn, early enough to preserve options. section 4.1 section 3.7

How Software Architecture Decision-Making covers it

How deep it goes
Explains decision trade-offs, feedback signals, reversibility, and scaling contingencies rather than implementation mechanics.
Examples
Uses an internal reporting capability and a system facing unexpectedly rapid demand growth.
What you can do after
Evaluate/understand when added architectural complexity has present value and when to defer it while preserving evolution options.
How it connects
Connects good-enough architecture with premature optimization, reversibility, feedback loops, scalability, security, and operational resilience.

Also explained in

Compare how 3 books explain overengineering →

Related concepts

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