Skip to main content

> durable_architecture_decisions_(adrs)

Durable Architecture Decisions (ADRs)

Why do modern systems require Architectural Decision Records (ADRs)?

THE SHORT ANSWER

To document the context and trade-offs of a decision so future teams understand why it was made, not just how.

Flashcards

Q1

What makes a good ADR?

Clear context, alternative options considered, the final decision, and the known negative consequences.
Q2

When does an architecture decision become immutable?

When the cost of refactoring the dependencies that rely on that decision exceeds the organization's budget.
Q3

How do microservices amplify organizational Conway's Law?

By physicalizing team communication boundaries into hard network boundaries and API contracts.

Related Concepts

Chaos Stack Field Notes FAQs

What are Chaos Stack Field Notes?

Chaos Stack Field Notes are technical flashcards that explain core engineering concepts quickly.

How are these different from topics?

Topics are broad thematic hubs that connect characters, episodes, and environments. Field Notes are short, direct Q&A flashcards for quick technical alignment.

AI Summary

This page covers Durable Architecture Decisions (ADRs) as a technical flashcard. Description: Why do modern systems require Architectural Decision Records (ADRs)?.