liveBook · Manning

Architectural decision

As explained in Vibe Engineering

An architectural decision is a choice about the structure, boundaries, interactions, or major technical direction of a software system.

An architectural decision chooses whether a service should exist, which trade-offs a system accepts, and whether an earlier direction still fits new evidence. It is judgment, not merely coding. section 10.8.1

Evaluate an architectural decision by asking:

  • Does the proposed service solve the right user problem, including needs hidden behind stated requirements? section 10.8.1
  • Does its trade-off remain correct after incidents and new system knowledge? section 10.8.1
  • Could automation propagate the decision into dependent services before anyone detects the mistake? section 10.8.1

Fast construction, expensive mistake

An agent builds a service in an afternoon, and other services integrate with it before review. If the architectural decision is wrong, the cost includes discarded code and subtle downstream effects—not merely the afternoon spent building. section 10.8.1

How Vibe Engineering covers it

How deep it goes
Distinguishes architectural judgment from coding and identifies amplified failure costs, but provides no formal decision procedure.
Examples
Uses a quickly generated service, prior incidents, hidden customer needs, and downstream integrations as decision evidence.
What you can do after
Evaluate architectural choices by revisiting trade-offs, requirements, incidents, and downstream propagation risks.
How it connects
Connects architectural decisions to services, trade-offs, requirements, incidents, downstream effects, and software agents.

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 Vibe Engineering. The section links point to the parts of the book it draws on.