What you will learn in Software Architecture Decision-Making
Trade-offs, constraints, and judgment that survive reality
Chapter by chapter
Chapter 1: The architecture that survives
The chapter introduction frames software architecture as decisions tested by delivery pressure and continually adapted to real constraints.
What you learn in chapter 1 →Chapter 2: The forces that shape architecture
The chapter introduction explains that architectural choices must account for interacting delivery, cost, capability, and risk pressures, and that making those pressures visible helps teams choose viable solutions.
What you learn in chapter 2 →Chapter 3: Good enough architecture vs. perfect architecture
The introduction frames good-enough architecture as a context-sensitive alternative to an ideal design, without abandoning quality.
What you learn in chapter 3 →Chapter 4: Design for evolution: architecture that survives change
The chapter introduction explains why architecture must remain effective as a system’s context changes, rather than merely preserve its initial design.
What you learn in chapter 4 →Concepts explained in this book
- architectural decisionAn architectural choice is a selected approach to a software system's technical structure or operation.
- tradeoffAn architectural trade-off is a deliberate compromise between competing qualities, benefits, costs, risks, or constraints in a system design.
- good-enough designGood-enough architecture is an intentionally sufficient design that meets important needs without pursuing an unattainable ideal of complete optimization or certainty.
- technical debtTechnical debt is the future cost or limitation created by expedient technical choices or by allowing design constraints to accumulate.
- evolvabilityEvolvability is the capacity of a software system or architecture to accommodate changing requirements, context, and implementation needs without disproportionate disruption or cost.
- feedbackFeedback is information from results, operation, stakeholders, or changing conditions that informs subsequent decisions and adaptations.
- overengineeringOverengineering is adding design complexity or capability beyond what current evidence and requirements justify.
- modular monolithA modular monolith is a deployable monolithic application organized into explicit internal modules with controlled boundaries.
- constraintA limitation or condition, such as time, cost, capability, risk, ownership, law, or organization, that restricts architectural choices.
- time pressureDelivery pressure is the practical force created by deadlines, limited resources, changing requirements, and the need to produce working software.
- team capabilityTeam capability is the collective knowledge, skills, experience, and capacity available to design, build, operate, and sustain a system.
- risk toleranceRisk tolerance is the amount and type of uncertainty, failure exposure, compliance exposure, and operational instability an organization is willing to accept.
- pressure briefA pressure brief is a lightweight decision record that captures architectural intent, forces, decision, consequences, feedback, and revisit conditions.
- time-to-marketTime-to-market is the elapsed period between initiating a product or feature and making it available to users.
- total cost of ownershipTotal cost of ownership is the full lifecycle cost of a system, including development, infrastructure, operations, support, security, recovery, and future change.
- continuous improvementA feedback loop is a recurring cycle in which information about results or changing conditions informs subsequent system decisions or adaptations.
- uncertaintyUncertainty is incomplete or changing knowledge about requirements, constraints, stakeholders, priorities, or future conditions that affect architectural choices.
- forcesAn architectural force is a contextual pressure or constraint that shapes which system designs are feasible.
- responsibilityThe explicit accountability for maintaining architectural coherence, revisiting assumptions, and protecting important system qualities over time.
- architecture decision recordAn architectural record is a durable record of a significant architectural decision and its rationale or consequences.
- event-driven architectureEvent-driven architecture is an architectural style in which components communicate and trigger work through events or messages.
- nonfunctional requirementA requirement describing a system quality or constraint, such as operability, security, performance, or adaptability, rather than a business function.
- compromise recordA compromise record is a lightweight book-specific record that captures an intentional delivery compromise, its reason, risk, owner, and revisit trigger.
- reversibilityReversibility is the degree to which an architectural decision can be changed or undone without disproportionate cost, risk, or disruption.
- premature optimizationPremature optimization is optimizing a system before sufficient evidence shows that the targeted problem is significant and worth the added cost.
- perfect architecturePerfect architecture is an idealized design presumed to be optimal across all relevant contexts, constraints, and consequences.
- last responsible momentThe last responsible moment is the latest point at which a decision can be made while preserving sufficient time to act responsibly and avoid unacceptable consequences.
- seamAn architectural seam is a deliberate boundary that allows part of a system to vary, be replaced, extended, tested, reconfigured, or modified with limited disruption to other parts.
- CV-driven developmentCV-driven development is selecting technologies or architectural patterns partly to enhance developers' résumés or career prospects rather than to meet the system's needs.
- fashion-driven architectureFashion-driven architecture is an architectural approach selected primarily because a technology or style is popular rather than because it addresses the system's actual needs.
- operational burdenOperational burden is the ongoing effort and complexity required to deploy, monitor, support, secure, troubleshoot, and recover a system.
- automated testingAn automated test is an executable check that evaluates software behavior without requiring manual execution of the check.
- architectural pressureArchitectural pressure is a force, constraint, or changing condition that influences software architecture and its decisions.
- operational readinessOperational readiness is the state in which a system and its responsible organization can deploy, operate, monitor, support, and recover it effectively.
- architectural decayArchitectural drift is the gradual divergence of a system's implemented structure from the assumptions, boundaries, and qualities originally intended.
- force assessment frameworkA force assessment framework is a structured method for evaluating the pressures and conditions that should influence an architectural decision.
- adapterAn adapter is a component that presents a consistent interface around an external dependency whose interface differs from the application's internal needs.
- abstractionAn abstraction is a deliberately simplified interface or representation that hides implementation details and permits variation behind a stable boundary.
- refactoringRefactoring is the disciplined restructuring of existing code without changing its externally observable behavior.
- scout philosophyThe scout rule is a code-maintenance practice of leaving code slightly better than it was found.
- authorizationAccess control is the enforcement of rules governing which identities or processes may access particular resources or operations.
- architectural rigorArchitectural rigor is the disciplined use of analysis, safeguards, verification, and operational controls to reduce the consequences of system failure.
- audit trailAn audit trail is a chronological record of actions, changes, approvals, or events that supports accountability and investigation.
- money calculationA financial calculation is a computation that determines monetary amounts, prices, balances, charges, or other financially significant values.
- principle of least privilegeLeast-privilege access grants each identity or process only the permissions required for its authorized tasks.
- safety-critical applicationA safety-critical system is a system whose failure can cause physical harm, loss of life, or other severe safety consequences.
- threat modelThreat modeling is the systematic identification and analysis of threats, attack paths, and mitigations for a system.
- replaceabilityReplaceability is the ability to substitute a system component or implementation without unacceptable effects on the rest of the system.
- guardrailA guardrail is a constraint or shared convention that enables local autonomy while preserving system-wide coherence.
- soft architectureSoft architecture, or architectural softness, is an architecture designed to accommodate change, redirection, and component replacement without disproportionate effort or risk.
- architectural fragmentationArchitectural fragmentation is the loss of coherence caused by duplicated, inconsistent, or poorly coordinated system approaches.
- communicationArchitectural communication is the deliberate exchange of architectural intent, decisions, trade-offs, and consequences among people involved in a system.
- project landscapeA project landscape is the set of current and planned initiatives, dependencies, shared resources, and surrounding systems that influence a project’s feasible decisions.
- architectural preparationArchitectural preparation is the deliberate creation of limited structures, contracts, records, or tests that reduce the cost and risk of responding to plausible future changes.
- cost of waitingCost of waiting is the worsening delivery, financial, operational, or strategic impact caused by delaying an architectural decision.
- delivery riskDelivery risk is the possibility that an unresolved decision or delayed action will block progress, force workarounds, or create unsafe shortcuts.
- future changeFuture change is a later alteration in requirements, usage, technology, organization, or operating conditions that an architecture may need to accommodate.
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.
