liveBook · Manning

Chapter 3: Good enough architecture vs. perfect architecture

What you will learn in chapter 3 of Software Architecture Decision-Making

The introduction frames good-enough architecture as a context-sensitive alternative to an ideal design, without abandoning quality.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The introduction frames good-enough architecture as a context-sensitive alternative to an ideal design, without abandoning quality.

Key terms: perfect architecture, good-enough architecture, quality, rigor, flexibility

3.1 Perfect architecture: the seduction of clean lines

This section shows how to resist elegant but speculative designs by solving the current problem, spending care on hard-to-reverse decisions, and keeping future changes affordable.

Key terms: perfection drift, future-proof, abstraction, reversibility, stable boundary, modular monolith, adapters, workflow boundaries, scout rule, refactoring

3.2 Good enough architecture: the art of trade-offs

Good-enough architecture matches rigor to present needs and consequences while keeping decisions open to feedback and change.

Key terms: good-enough architecture, minimum floor, real constraints, overengineering, oversimplification, rigor, cost of reversal, feedback from reality, trade-offs, reversibility

3.3 Architecture reality: evolution as a cornerstone

The section explains how to deliver useful software under uncertainty while keeping architectural decisions proportionate to what is known and how costly they would be to reverse.

Key terms: good-enough and evolvable approach, ideal end state, early slice of value, lightweight decision log, difficult to reverse, stability now, cheap to change, sequential model, late validation, iterative methods

3.4 The economics of good enough

This section judges good-enough architecture by the value it delivers relative to its costs, risks, and consequences, rather than by technical elegance alone.

Key terms: good-enough architecture, consequence, return on investment, value, organization’s context, directly, indirectly, good enough, shortcuts, standards

3.5 When perfection actually matters

This section explains how to apply stronger architectural rigor to decisions whose failure consequences justify it, while allowing bounded compromises elsewhere.

Key terms: decision rigor rubric, consequence model, high-rigor side, perfection, availability target, business impact of downtime, revisit trigger, simpler API style, lightweight automation, safeguards

3.6 How to know if architecture is “good enough”

This section gives architects a lightweight way to judge whether a design is sufficient for its context without overbuilding or falling below an acceptable minimum.

Key terms: good enough, minimum standard, overbuild risk, underbuild risk, pressure brief, good-enough review, forces, decision, revisit trigger

3.7 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 2: The forces that shape architecture Chapter 4: Design for evolution: architecture that survives change →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.