???? ADR – Architecture Decision Record

ADR stands for Architecture Decision Record, is a document where decisions are made, the place where we put all the information about something that involves your architecture, could be a decision to start using new software, could be a decision to choose a new cloud provider, etc.

Usually, this decision comes after a POC where we collect all the information we need to support us to make the best decision possible.

I personally believe that all big decisions should be made involving the whole team, different points of view will come up and could help and drive the team to take the right decision. I will leave down below a template with all points that I think are needed to make a good decision, feel free to adapt it to your own need, and if you use Notion you can duplicate easily the template.

Notion template:

https://www.notion.so/carlospcastro/ADR-Architecture-Decision-Record-3f69412ab03443a9bb3094b3acbabe74

ADR – Number X

StatusACCEPTED
OwnerSomeone responsible to facilitate meetings
DecidersTeam A, Team B and Team C
Date27.05.2022
OutcomeWe as a team decided to you XXX as a cloud provider

Meeting notes:

All the notes collected during a meeting to discuss this specific ADR

Tasks:

  • Ticket numbers that are somehow involved in this ADR.

Context and what problem will be solved

  • A clear context and what is the main reason to create this ADR, what is the problem that needs to be solved.

Decision Drivers

What are the main topics that drive a decision, positive or negative decision.

Considered Options

Other options have been considered? If yes, here is the place to note them down.

Pros and Cons of the Options

Option 1: Use cloud provider A with subscription model A

  • ✅  Good because …
  • ✅  Good because …
  • Bad because …
  • Bad because …

Option 2: Use cloud provider A with subscription model B

  • ✅  Good because …
  • ✅  Good because …
  • ????  Bad because …
  • ????  Bad because …

Option 3: Use cloud provider B with subscription model A

  • ✅  Good because …
  • ✅  Good because …
  • ????  Bad because …
  • ????  Bad because …

And so on and so forth

Decision Outcome

Here is the place to state the decision.

Positive Consequences

  • More flexibility
  • Cheaper solution

Negative Consequences

  • More dependency on the cloud provider
  • More complex

Links

Links that helped you along with the research, POC’s, etc.

Related Post

One thought on “???? ADR – Architecture Decision Record

  1. Thanks for sharing your ideas about ADR – ARCHITECTURE DECISION RECORD. Much appreciated Carlos.
    I will consider using this technique with the team.

Comments are closed.