liveBook · Manning

Architectural decision

Also called architecture decisions, architectural choice

An architectural decision is a significant choice about the structure, behavior, interactions, or technical constraints of a software system.

How 6 Manning books explain it

Software Architecture Decision-Making

An architectural choice is a selected approach to a software system's technical structure or operation.

How it is used
Frames technical structure and operation as choices negotiated against delivery, organizational, and operational constraints.
How deep it goes
Explains decision-making through forces, trade-offs, feedback, and a six-question assessment, without prescribing a universal technical solution.
Examples
Uses a small-team reporting capability and contrasts managed services, self-operated platforms, serverless, containers, and integration styles.
What you can do after
Evaluate/understand architectural options by making forces, ownership, trade-offs, and changing consequences visible before commitment.

Read how Software Architecture Decision-Making explains architectural decision →

Architecture Modernization: Socio-technical alignment of software, strategy, and structure

An architectural decision is a choice about the structure, behavior, or governing constraints of a software architecture.

How it is used
Aligns architecture, product strategy, and team structures when choosing among competing models.
How deep it goes
Moves from competing models into domain detail and strategic complexity, rejecting high-level views as sufficient for granular decisions.
Examples
Uses Vinted’s competing category models, EventStorming, context mapping, Core Domain Charts, and Wardley Maps.
What you can do after
Evaluate architectural options by connecting domain complexity and team structures to product goals and long-term outcomes.

Read how Architecture Modernization: Socio-technical alignment of software, strategy, and structure explains architectural decision →

Microservices Patterns, Second Edition

The process of choosing and governing the fundamental structure, relationships, and principles of a software system.

How it is used
Frames software architecture as accumulated decisions that solve problems and shape subsequent design.
How deep it goes
Decomposes decision elements and architectural effects, then discusses ownership and timing without prescribing a detailed decision procedure.
Examples
Uses a layered design with web/api, domain, and infrastructure layers, and compares four approaches to decision ownership.
What you can do after
Evaluate decision ownership and choose a simple architecture that solves current problems while allowing evidence-based evolution.

Read how Microservices Patterns, Second Edition explains architectural decision →

Collaborative Software Design: How to facilitate domain modeling decisions

An architectural decision is a significant choice about the structure or organization of a software system together with its context and consequences.

How it is used
Frames significant system-structure choices as decisions whose reasoning should remain visible beyond the immediate outcome.
How deep it goes
Distinguishes decision quality from outcome quality and specifies ADR fields, while leaving the ADR format adaptable.
Examples
Uses monolith-versus-microservices choices and an ADR for redesigning a big ball of mud around the “Anytime, Anywhere” campaign.
What you can do after
Apply ADRs to document architectural reasoning, consequences, status, and context for later review.

Read how Collaborative Software Design: How to facilitate domain modeling decisions explains architectural decision →

Grokking Software Architecture

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

How it is used
Guides deliberate choices that shape a system and affect its future development.
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.

Read how Grokking Software Architecture explains architectural decision →

Vibe Engineering

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

How it is used
Frames system direction and boundaries as judgment problems that automation cannot safely delegate.
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.

Read how Vibe Engineering explains architectural decision →

Also covered in

What to know first

Related concepts

Questions about architectural decision

What is architectural decision?

An architectural decision is a significant choice about the structure, behavior, interactions, or technical constraints of a software system.

Which Manning books explain architectural decision?

Software Architecture Decision-Making, Architecture Modernization: Socio-technical alignment of software, strategy, and structure, Microservices Patterns, Second Edition, Collaborative Software Design: How to facilitate domain modeling decisions, Grokking Software Architecture and Vibe Engineering.

What should I know before learning architectural decision?

Manning books that teach architectural decision usually introduce microservice architecture, contract, distributed system and monolithic architecture first.

What is the difference between architectural decision and result?

An architectural decision is a significant choice about the structure, behavior, interactions, or technical constraints of a software system. A result is an outcome, observation, or value produced or observed by an action, event, process, or evaluation.

What kinds of architectural decision are there?

Kinds of architectural decision include architecting.

What is architectural decision part of?

Architectural decision is part of software architecture. Software architecture is the significant structure of a software system, including its components, relationships, and design decisions that shape how the system is built and behaves.

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.