Architectural decision
An architectural decision is a choice about the significant structure, behavior, interactions, or technical constraints of a software system.
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.
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.
Related concepts
- architecture decision recordused by · An architecture decision record is a document that captures an architectural decision, its context, rationale, and consequences.
- architecture advice processconfigured by · The architecture advice process is a decision-making practice in which a decision-maker seeks input from affected stakeholders and subject-matter experts.
- solutionuses · A solution is an answer, approach, or assignment intended to address a problem or meet specified objectives or requirements.
- risk toleranceconfigured by · Risk tolerance is the degree and types of uncertainty or potential adverse outcomes that an individual or organization is willing to accept while pursuing objectives.
- model architecturepart of · The structural organization of a computational system’s components, relationships, and operations that determines how it processes information or 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.