51 lines
945 B
Markdown
51 lines
945 B
Markdown
# ADR — Architecture Decision Record
|
|
|
|
## Decision title
|
|
|
|
<!-- Brief title (e.g. "Using PostgreSQL as primary database") -->
|
|
|
|
## Status
|
|
|
|
<!--
|
|
Proposed | Approved | Deprecated | Superseded by [ADR-XXX]
|
|
-->
|
|
|
|
## Context
|
|
|
|
<!--
|
|
Describe the problem we are solving. What are the circumstances, constraints, and requirements?
|
|
-->
|
|
|
|
## Decision
|
|
|
|
<!--
|
|
What solution did we choose and why? Describe the architectural approach.
|
|
-->
|
|
|
|
## Rationale
|
|
|
|
<!--
|
|
Why did we choose this solution? What are the main benefits compared to alternatives?
|
|
-->
|
|
|
|
## Alternatives
|
|
|
|
<!--
|
|
What other options did we consider and why did we reject them?
|
|
-->
|
|
|
|
## Consequences
|
|
|
|
<!--
|
|
- What changes? What needs to be done?
|
|
- What are the trade-offs (e.g. higher complexity for lower latency)?
|
|
- Impact on other teams / systems?
|
|
-->
|
|
|
|
## Metadata
|
|
|
|
- **Date**: YYYY-MM-DD
|
|
- **Author**: name
|
|
- **Stakeholders**: team A, team B
|
|
- **References**: [link to design doc], [link to issue]
|