Architecture decision records (ADR) in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an Architecture Decision Record (ADR)?

An ADR is a document that captures important architectural decisions made during a project. It explains the decision, the reasons behind it, and its consequences.

beginner

Why are ADRs important in microservices architecture?

ADRs help teams keep track of why certain design choices were made, making it easier to understand, maintain, and evolve microservices over time.

intermediate

What key elements should an ADR contain?

An ADR should include: the decision title, context, the decision itself, alternatives considered, and the consequences of the decision.

beginner

How does an ADR help new team members?

It provides clear explanations of past decisions, helping new members understand the system design without needing lengthy meetings or guesswork.

intermediate

When should an ADR be created?

An ADR should be created whenever a significant architectural decision is made that affects the system's design or behavior.

What does an ADR primarily document?

A User interface designs

B Architectural decisions and their reasons

C Code implementation details

D Testing procedures

ADRs focus on documenting architectural decisions and why they were made.

Which of the following is NOT typically part of an ADR?

A Decision title

B Context and background

C Consequences of the decision

D Code snippets

Code snippets are usually not included in ADRs; ADRs focus on decisions and reasoning.

When is the best time to write an ADR?

A At the end of the project

B Only when problems occur

C After a major architectural decision is made

D Before starting any work

ADRs should be written right after important architectural decisions to capture context and reasoning.

How do ADRs benefit microservices teams?

A By tracking architectural decisions for clarity and future reference

B By replacing all documentation

C By automating deployment

D By managing user accounts

ADRs help teams understand past decisions, improving clarity and maintenance.

Which is a common consequence documented in an ADR?

A Impact on system scalability

B User feedback scores

C Marketing strategies

D Employee schedules

ADRs document consequences like how a decision affects scalability, performance, or maintainability.

Explain what an Architecture Decision Record (ADR) is and why it is useful in microservices.

Think about how teams remember important design choices.

Describe the typical structure of an ADR and what each part contains.

Consider the story an ADR tells about a decision.