Recording Architectural Decisions
Understand the importance of architectural decision records (ADRs) in maintaining clear documentation of critical design choices. Explore how to use ADRs to log decisions such as infrastructure changes, technology adoption, and design patterns. Gain practical insights into keeping an architecture decision log to support project clarity and evolution within event-driven architecture.
We'll cover the following...
Moving to the implementation side, we now face decision-making issues on how this application will be developed. The decisions that we make will have lasting repercussions for a project, and over the life of the project, the motivations for why a decision was made can be lost.
Enter the architecture decision record. The most popular format for these records comes from Michael Nygard, who suggested the following format:
# {RecordNum}. {Title}## ContextWhat is the issue that we're seeing that is motivating thisdecision or change?## DecisionWhat is the change that we're proposing and/or doing?## StatusProposed, Accepted, Rejected, Superseded, Deprecated## ConsequencesWhat becomes easier or more difficult to do because of thischange
An architectural decision record should be ...