liveBook · Manning

Architecture decision record

Also called ADR, architectural decision record

An architecture decision record is a durable document that captures a significant architectural decision, its context, rationale, and consequences.

How 7 Manning books explain it

Grokking Software Architecture

A document that records an architectural decision, its context, considered alternatives, and rationale.

How it is used
Captures significant architectural choices and their reasoning after options and tradeoffs have been considered.
How deep it goes
Provides a decision-worthiness test, a field-by-field example, and guidance on recording risks and review triggers.
Examples
Works through a session-storage choice and assigns a security audit with an ADR deliverable.
What you can do after
Practice writing a concise ADR that explains a choice, its alternatives, tradeoffs, and risks.

Read how Grokking Software Architecture explains architecture decision record →

Authorization in Action

An architectural decision record is a version-controlled document that captures the context, rationale, decision, consequences, and related artifacts for an architectural choice.

How it is used
Connects authorization policy choices to organizational intent and governance.
How deep it goes
Defines the record and its contents, then describes policy links and governance use without presenting a complete record.
Examples
Uses an authorization policy for personal data to illustrate regulatory-control references, tests, and audit evidence.
What you can do after
Practice documenting access decisions and linking policies to their rationale for review and audit.

Read how Authorization in Action explains architecture decision record →

Collaborative Software Design: How to facilitate domain modeling decisions

A structured document that records an architectural decision, its context, and its consequences.

How it is used
Formalizes collaborative architectural choices for future reference, stakeholder communication, and continued design feedback.
How deep it goes
Defines five core fields and flexible formats, then connects ADRs to tradeoffs, stakeholder inclusion, diagrams, and living documentation.
Examples
Uses a BigScreen architecture redesign, an ADR canvas, Pros-Cons-and-Fixes lists, and distilled collaborative modeling diagrams.
What you can do after
Document decisions clearly, involve affected stakeholders asynchronously, and update records as context and understanding change.

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

Software Architecture Decision-Making

An architectural record is a durable record of a significant architectural decision and its rationale or consequences.

How it is used
Preserves rationale and trade-offs for significant architectural choices as teams and systems evolve.
How deep it goes
Defines a lightweight record structure, consequences, statuses, and review triggers without prescribing a tool or formal process.
Examples
Uses Markdown repository records and an open decision log for deployment, repository organization, and data ownership decisions.
What you can do after
Apply it by recording consequential decisions, alternatives, trade-offs, and conditions that trigger review.

Read how Software Architecture Decision-Making explains architecture decision record →

Claude at Work

An architecture decision record is a document that captures a significant software architecture decision, its rationale, consequences, and alternatives.

How it is used
Preserves the rationale behind significant technical decisions for future project members.
How deep it goes
Defines a concise record structure and demonstrates generation, but leaves deeper decision research and challenge as possible extensions.
Examples
Uses Redis Streams over Kafka and a switch from .NET to Python as decision examples.
What you can do after
Apply the adr-writer skill to generate an ADR in a project’s docs/adr directory.

Read how Claude at Work explains architecture decision record →

Build High Value Software Systems

An architecture decision record is a concise document that records an architectural decision, its rationale, and its consequences.

How it is used
Preserves architectural intent and decision history for later review and root-cause analysis.
How deep it goes
Details decision-log fields and explains how recorded constraints distinguish a flawed decision from one overtaken by change.
Examples
Uses a deferred internal-API versioning decision, triggered by a partner integration and resolved using observed API usage.
What you can do after
Diagnose incidents by tracing decisions to their original rationale and constraints, then assess whether conditions have changed.

Read how Build High Value Software Systems explains architecture decision record →

The Design of Web APIs, Second Edition

An architectural decision record is a documented record of a significant software or API design decision, including its rationale, alternatives, and consequences.

How it is used
Records and justifies significant API design choices, preserving reasoning and supporting API design guidelines.
How deep it goes
Explains ADR contents and workflow through a completed example, while deferring broader formats, practices, and tools.
Examples
Uses resource ID property naming and a proposed numeric-ID rule to illustrate decision analysis.
What you can do after
Apply an ADR to record a problem, decision, options, reasoning, pros and cons, consequences, and sources.

Read how The Design of Web APIs, Second Edition explains architecture decision record →

Also covered in

What to know first

Related concepts

Questions about architecture decision record

What is architecture decision record?

An architecture decision record is a durable document that captures a significant architectural decision, its context, rationale, and consequences.

Which Manning books explain architecture decision record?

Grokking Software Architecture, Authorization in Action, Collaborative Software Design: How to facilitate domain modeling decisions, Software Architecture Decision-Making, Claude at Work, Build High Value Software Systems and The Design of Web APIs, Second Edition.

What should I know before learning architecture decision record?

Manning books that teach architecture decision record usually introduce context, architectural decision, decision making and deployment pipeline first.

What are the parts of architecture decision record?

Architecture decision record includes business problem.

What is architecture decision record also called?

Architecture decision record is also called ADR or architectural decision record.

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.