architecture-decision-records

原文涵盖的主题

• Architecture Decision Records
• When to Use This Skill
• Core Concepts
• 1. What is an ADR?
• 2. When to Write an ADR
• 3. ADR Lifecycle
• Templates
• Template 1: Standard ADR (MADR Format)

Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions. Making significant architectural decisions Documenting technology choices Recording design trade-offs Onboarding new team members Reviewing historical decisions Establishing decision-making processes An Architecture Decision Record captures: Context: Why we needed to make a decision Decision: What we decided Consequences: What happens as a result | Write ADR | Skip ADR | | -------------------------- | ---------------------- | | New framework adoption | Minor version upgrades | | Database technology choice | Bug fixes | | API design patterns | Implementation details | | Security architecture | Routine maintenance | | Integration patterns | Configuration changes | OrderCreated { orderId, customerId, items[], timestamp } OrderItemAdded { orderId, item, timestamp } OrderItemRemoved { orderId, itemId, timestamp } PaymentReceived { orderId, amount, paymentId, timestamp } OrderShipped { orderId, trackingNumber, timestamp } Write ADRs early - Before implementation starts Keep them short - 1-2 pages maximum Be hone

这里只展示节选，请以完整原文和当前要求为准。