- Documents a decision that addresses a functional or non functional requirement that is architecturally significant
- An Architecturally Significant Requirement is a requirement that has a measurable effect on a software system’s architecture and quality.
- Solution to a problem can start as an RFC to facilitate discussion and collaboration within the community members. The outcome of the RFC must be recorded as an ADR
- ADR can also be used to document patterns/standards that forms naturally. Patterns can be identified when doing code reviews
- Status
- DRAFT
- ACCEPTED
- SUPERSEEDED by ADR-xxx
| Markdown |
|---|
# 1ADR-000001. Use Kafka as the distributed event streaming platform Date: 2022-05-07 ## Status Accepted ## Background/Context ## Decision ## Consequences * Pros * Cons |
Resources
https://github.com/npryce/adr-tools
Questions
- If we are going to use wiki, can we use tags ?