liveBook · Manning

What you will learn in Software Architecture Decision-Making

Trade-offs, constraints, and judgment that survive reality

by Dominik Włodarz · Manning Early Access Program (MEAP)

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.

1.1 How architecture really works · 1.2 Architectural responsibility is not a job title · 1.3 Architecture as decision-making, not design · 1.4 Turning ambiguity into technical objective · 1.5 Communication is an architectural tool · 1.6 Architecture as a living responsibility · 1.7 Architecture as continuous decision-making · 1.8 Summary

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.

2.1 Time-to-market (TTM) · 2.2 Cost and budget limitations · 2.3 Team skills and maturity · 2.4 Risk tolerance · 2.5 Emerging accelerators: AI and speed compression · 2.6 A practical force-assessment framework · 2.7 Summary

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.

3.1 Perfect architecture: the seduction of clean lines · 3.2 Good enough architecture: the art of trade-offs · 3.3 Architecture reality: evolution as a cornerstone · 3.4 The economics of good enough · 3.5 When perfection actually matters · 3.6 How to know if architecture is “good enough” · 3.7 Summary

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.

4.1 Systems never sit still · 4.2 Evolution as a first-class architectural quality · 4.3 Feedback loops and sensing change · 4.4 Designing with future change in mind · 4.4.1 Avoiding premature commitment · 4.4.2 Designing seams · 4.4.3 The Strangler Fig pattern · 4.4.4 Architecture decision records (ADR) · 4.5 Keeping architecture soft, not rigid · 4.5.1 Modular monolith vs. distributed monolith · 4.5.2 Avoiding accidental complexity · 4.5.3 Team maturity matters · 4.5.4 Backward compatibility and versioning · 4.5.5 Event-driven vs. request-driven evolvability · 4.6 Cloud-specific evolution traps · 4.7 Designing for incremental replaceability · 4.8 Evolution as collaboration · 4.9 The architect’s role in evolutionary systems · 4.10 Summary

What you learn in chapter 4 →

Concepts explained in this book

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.