liveBook · Manning

Architectural decision

As explained in Grokking Software Architecture

An architectural decision is a choice that materially shapes a software system's structure, behavior, or quality attributes.

An architectural decision is a choice that makes building, shipping, or changing a system significantly easier or harder. It might shape the system’s structure, behavior under stress, or ability to evolve. Choosing a database counts; not every line of code needs a formal review. section 1.3

Figure 1.2 A software system, like a food truck, has a distinct structure. The API is the service window, the business logic is the cook, and dependencies like the database and cache are the grill and fridge.

A food truck makes system structure tangible: the API is the service window, business logic is the cook, and the database and cache are the grill and fridge. Choices also affect what happens during a rush, when a dependency fails, or when the menu changes. section 1.3

There is no universally perfect architecture. A decision involves tradeoffs, such as shipping sooner versus making future changes easier. A useful decision records not just what was chosen, but why and what consequences follow. section 1.10

Make a small decision defensible:

  • Name the technical choice and two realistic options. section 1.8.1
  • For each option, state one benefit and one cost or risk. section 1.8.1
  • Choose an option and give a one-sentence rationale; for larger decisions, use Spark → Inquiry → Sketch → Options → Decision. section 1.8.1 section 1.10

How Grokking Software Architecture covers it

How deep it goes
Defines a significance test and a five-step process, while reserving formal review for choices that warrant it.
Examples
Uses a food-truck system analogy and a two-option exercise comparing benefits, costs, and rationale.
What you can do after
Apply the five-step process to compare options, choose deliberately, and document the rationale and consequences.
How it connects
Connects software architecture with tradeoffs, quality attributes, and architecture decision records.

Also explained in

Compare how 6 books explain architectural decision →

Related concepts

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.