Back to Details

architecture-decision-record

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Architecture Decision Record

架构决策记录（ADR）

Step 1: Understand the decision

步骤1：理解决策

Ask the user:
What architecture decision do you need to document? Please share:
  • Decision title (e.g., "Use Aurora Serverless v2 for the orders database")
  • Context — What problem are you solving? What constraints exist?
  • Options considered (at least 2) — or ask me to suggest alternatives
If the user has already described the decision, proceed directly.
询问用户：
您需要记录什么架构决策？请分享：
  • 决策标题（例如：“为订单数据库使用Aurora Serverless v2”）
  • 背景——您要解决什么问题？存在哪些约束条件？
  • 考虑的选项（至少2个）——或者让我推荐替代方案
如果用户已经描述了决策内容，请直接进入下一步。

Step 2: Evaluate options against WA pillars

步骤2：基于Well-Architected支柱评估选项

For each option, assess impact on all six pillars:
PillarOption AOption BOption C
Operational Excellence
Security
Reliability
Performance Efficiency
Cost Optimization
Sustainability
Use: ✅ Positive | ➖ Neutral | ⚠️ Trade-off | ❌ Negative
针对每个选项，评估其对六大支柱的影响：
支柱选项A选项B选项C
卓越运营
安全
可靠性
性能效率
成本优化
可持续性
使用符号：✅ 正面影响 | ➖ 中性影响 | ⚠️ 需要权衡 | ❌ 负面影响

Step 3: Identify trade-offs

步骤3：明确权衡因素

For the recommended option, explicitly state:
  • What you gain
  • What you give up
  • Under what conditions the decision should be revisited
针对推荐选项，明确说明：
  • 获得的收益
  • 做出的让步
  • 需重新审视该决策的条件

Step 4: Produce the ADR

步骤4：生成ADR

Output using the standard ADR format:
markdown
undefined
使用标准ADR格式输出：
markdown
undefined

ADR-{number}: {Decision Title}

ADR-{number}: {决策标题}

Status

状态

{Proposed | Accepted | Deprecated | Superseded by ADR-X}
{提议中 | 已通过 | 已弃用 | 被ADR-X取代}

Date

日期

{YYYY-MM-DD}
{YYYY-MM-DD}

Context

背景

{What is the problem? What forces are at play? What constraints exist?}
{问题是什么？有哪些影响因素？存在哪些约束条件？}

Decision

决策

{What is the change that we're proposing and/or doing?}
{我们提议或正在执行的变更是什么？}

Options Considered

考虑的选项

Option 1: {name}

选项1：{名称}

  • Description: {how it works}
  • Pros: {benefits}
  • Cons: {drawbacks}
  • WA Impact: {pillar impacts}
  • 描述：{工作原理}
  • 优势：{收益}
  • 劣势：{弊端}
  • Well-Architected影响：{各支柱影响}

Option 2: {name}

选项2：{名称}

  • Description: {how it works}
  • Pros: {benefits}
  • Cons: {drawbacks}
  • WA Impact: {pillar impacts}
{Additional options as needed}
  • 描述：{工作原理}
  • 优势：{收益}
  • 劣势：{弊端}
  • Well-Architected影响：{各支柱影响}
{按需添加更多选项}

Well-Architected Impact

Well-Architected影响

PillarImpactNotes
Operational Excellence{+/-/neutral}{why}
Security{+/-/neutral}{why}
Reliability{+/-/neutral}{why}
Performance Efficiency{+/-/neutral}{why}
Cost Optimization{+/-/neutral}{why}
Sustainability{+/-/neutral}{why}
支柱影响说明
卓越运营{正面/中性/负面}{原因}
安全{正面/中性/负面}{原因}
可靠性{正面/中性/负面}{原因}
性能效率{正面/中性/负面}{原因}
成本优化{正面/中性/负面}{原因}
可持续性{正面/中性/负面}{原因}

Trade-offs

权衡因素

{What are we explicitly accepting as a trade-off?}
{我们明确接受的权衡内容是什么？}

Consequences

影响结果

{What becomes easier or harder because of this decision?}
{该决策会让哪些事情变得更容易或更困难？}

Implementation Notes

实施说明

  • Effort: {Low / Medium / High}
  • Timeline: {estimated}
  • AWS Services: {key services involved}
  • Reversibility: {Easy / Hard / Irreversible}
  • 工作量：{低 / 中 / 高}
  • 时间线：{预估时长}
  • AWS服务：{涉及的核心服务}
  • 可逆性：{易 / 难 / 不可逆}

Review Triggers

复审触发条件

{Under what conditions should this decision be revisited?}
  • {trigger 1}
  • {trigger 2}
undefined
{在哪些条件下需要重新审视该决策？}
  • {触发条件1}
  • {触发条件2}
undefined

Step 5: Offer next steps

步骤5：提供后续选项

After producing the ADR, offer:
Would you like me to:
  • Add more options to evaluate?
  • Deep-dive into a specific pillar's impact?
  • Create an implementation plan for the chosen option?
  • Generate IaC for the decision?
  • Draft a follow-up ADR for a related decision?
生成ADR后，提供以下选项：
您是否希望我：
  • 添加更多评估选项？
  • 深入分析某一特定支柱的影响？
  • 为选定的选项创建实施计划？
  • 生成该决策对应的基础设施即代码（IaC）？
  • 为相关决策起草后续ADR？