本文由 AI 分析生成
建立時間： 2026-03-27 來源： https://www.infoq.com/articles/framework-architectural-decisions/
Summary
Grygoriy Gonchar (heycar) proposes a three-component framework for governing architectural decisions at an organization level: (1) internal Technology Radar — maturity assessment of technologies (Assess/Trial/Adopt/Hold); (2) Technology Standards — consistent rules for crosscutting concerns; (3) Architecture Decision Records (ADRs) — immutable per-decision documentation. Each layer operates at a different scope and time horizon.
Gonchar 提出三組件架構決策治理框架：（1）內部技術雷達——技術成熟度評估（評估/試行/採納/暫停）；（2）技術標準——橫切關注點的一致規則；（3）架構決策記錄（ADR）——不可變的單項決策文件。每層在不同範圍和時間跨度下運作。
Key Points
- Tech Radar: Assess → Trial (single production use case) → Adopt (green light for all) → Hold (has replacement strategy). The Radar helps teams know what’s approved without asking each time
- Technology Standards: cover crosscutting concerns (logging format, REST API conventions, QA gates) — the “paved road” concept; bad standards = bureaucratic theater, good standards = make the right thing the default
- ADRs: capture why a one-time decision was made — immutable documents, so revisiting creates a new ADR. Prevents “why did we choose X?” archaeology months later
- Scope separation: Radar/Standards govern general technology choices; ADRs govern specific one-time decisions — using both avoids duplication while maintaining full coverage
- Culture signal: the degree of team autonomy to change the Radar/Standards reveals the engineering culture. High consistency = restrictive ladder; radical autonomy = teams fork freely
Insights
The most commonly missing piece in engineering orgs is the Technology Standards layer — most teams have either informal “standards” or no standards at all. ADRs without Standards means each ADR has to relitigate basic conventions. Standards make ADR reviews faster because the large scope decisions are pre-decided. The insight about “paved roads” is key: automate quality gates (linters, fitness functions) so developers get standards enforcement without needing to memorize them.
Connections
Raw Excerpt
Together, the Technology Radar, Technology Standards, and ADRs form a framework that provides a clear and consistent approach to making architectural decisions. The degree of freedom your team has, and the process to change the Radar, Standards, or ADRs, will shape your engineering culture.