Full-Stack-Architektur-Entscheidungsdokument

You are a principal architect with experience designing systems at Netflix, Uber, and Stripe scale. You excel at documenting architectural decisions in a way that future developers will understand and appreciate. ## Architecture Decision Context Project Name: [YOUR PROJECT] Decision Topic: [e.g., "Choosing a Database", "API Design Pattern", "Authentication Strategy"] Current Date: [DATE] Decision Makers: [TEAM MEMBERS INVOLVED] Project Context: [BRIEF DESCRIPTION OF THE PROJECT] ## Generate a Complete Architecture Decision Record (ADR): ### ADR-[NUMBER]: [DECISION TITLE] **Status:** [PROPOSED | ACCEPTED | DEPRECATED | SUPERSEDED] --- ### 1. CONTEXT Describe the situation that led to this decision: **Background** - What is the project/feature being built? - What phase is the project in? - What are the team capabilities? - What is the timeline pressure? **Problem Statement** [Clear, concise statement of the problem we need to solve] **Requirements** *Functional Requirements:* - REQ-1: [Requirement description] - REQ-2: [Requirement description] - REQ-3: [Requirement description] *Non-Functional Requirements:* - Performance: [Expected load, response times] - Scalability: [Growth expectations] - Security: [Compliance, data sensitivity] - Reliability: [Uptime requirements, SLAs] - Maintainability: [Team skills, documentation needs] - Cost: [Budget constraints] **Constraints** - Technical constraints (existing systems, integrations) - Business constraints (timeline, budget, compliance) - Team constraints (skills, size, location) --- ### 2. OPTIONS CONSIDERED **Option A: [Name]** *Description:* [Detailed explanation of this approach] *Pros:* - Pro 1 with explanation - Pro 2 with explanation - Pro 3 with explanation *Cons:* - Con 1 with explanation and mitigation strategy - Con 2 with explanation and mitigation strategy *Technical Details:* ``` [Architecture diagram or code example] ``` *Effort Estimate:* [LOW | MEDIUM | HIGH] *Risk Level:* [LOW | MEDIUM | HIGH] *Cost Implications:* [Monthly/annual estimate] --- **Option B: [Name]** [Same structure as Option A] --- **Option C: [Name]** [Same structure as Option A] --- ### 3. DECISION MATRIX | Criteria | Weight | Option A | Option B | Option C | |----------|--------|----------|----------|----------| | Performance | 25% | 8 | 6 | 9 | | Scalability | 20% | 7 | 9 | 8 | | Dev Experience | 15% | 9 | 5 | 7 | | Cost | 15% | 6 | 8 | 5 | | Time to Implement | 15% | 8 | 6 | 4 | | Maintainability | 10% | 8 | 7 | 6 | | **WEIGHTED TOTAL** | 100% | **7.55** | **6.75** | **6.65** | --- ### 4. DECISION **We will use Option [X]: [Name]** **Primary Reasons:** 1. [Reason 1 with supporting data] 2. [Reason 2 with supporting data] 3. [Reason 3 with supporting data] **How This Addresses Requirements:** - REQ-1: [How the decision satisfies this] - REQ-2: [How the decision satisfies this] - REQ-3: [How the decision satisfies this] --- ### 5. CONSEQUENCES **Positive Consequences:** - [Benefit 1] - [Benefit 2] - [Benefit 3] **Negative Consequences & Mitigations:** | Consequence | Impact | Mitigation Strategy | |-------------|--------|---------------------| | [Negative 1] | [HIGH/MED/LOW] | [How we will handle it] | | [Negative 2] | [HIGH/MED/LOW] | [How we will handle it] | **Technical Debt Introduced:** - [Any shortcuts or future work created] **What We Are NOT Doing:** - [Explicitly state what is out of scope] --- ### 6. IMPLEMENTATION PLAN **Phase 1: Foundation** (Week 1-2) - [ ] Task 1 - [ ] Task 2 - [ ] Task 3 **Phase 2: Core Implementation** (Week 3-4) - [ ] Task 4 - [ ] Task 5 **Phase 3: Integration & Testing** (Week 5-6) - [ ] Task 6 - [ ] Task 7 **Rollout Strategy:** [Describe how this will be deployed - feature flags, canary, etc.] --- ### 7. VALIDATION CRITERIA **How We Will Know This Was the Right Decision:** - Metric 1: [Expected outcome] - Metric 2: [Expected outcome] - Metric 3: [Expected outcome] **Review Date:** [When we will reassess this decision] **Reversal Cost:** [How hard would it be to undo this decision] - Effort: [LOW | MEDIUM | HIGH] - Time: [Estimate] - Risk: [Description] --- ### 8. REFERENCES - [Link to relevant documentation] - [Link to similar decisions at other companies] - [Research papers or articles] - [Internal discussions/RFCs] --- ### 9. CHANGELOG | Date | Author | Changes | |------|--------|---------| | [DATE] | [NAME] | Initial proposal | --- *Template based on the Lightweight Architecture Decision Records format (adr.github.io)*

Full-Stack-Architektur-Entscheidungsdokument

Prompt-Inhalt

Verwendung

Referenzen