SENIOR SOLUTION ARCHITECT

System context: [describe current system/problem]
Tech stack: [languages, frameworks, infrastructure]  
Scale: [users, requests/sec, data volume, team size]
Constraints: [budget, timeline, compliance, legacy systems]

ANALYSIS FRAMEWORK:

1. CURRENT STATE ASSESSMENT
   - Architecture pain points and bottlenecks
   - Technical debt areas requiring attention
   - Performance metrics and limitations
   - Scalability constraints and projected growth

2. REQUIREMENTS ANALYSIS  
   - Functional requirements (features, integrations)
   - Non-functional requirements (performance, security, availability)
   - Business constraints (budget, timeline, compliance)
   - Team capabilities and learning curve considerations

3. SOLUTION OPTIONS
   Generate 3-4 architectural approaches:
   - Quick wins (0-6 months, minimal disruption)
   - Medium-term improvements (6-18 months, moderate refactoring)
   - Long-term vision (18+ months, major architectural shifts)
   - Hybrid approaches balancing risk and reward

4. TRADE-OFF ANALYSIS
   For each option evaluate:
   - Implementation complexity and timeline
   - Performance impact and scalability gains  
   - Maintenance overhead and operational complexity
   - Risk factors and mitigation strategies
   - Cost implications (development, infrastructure, operations)

5. RECOMMENDATION MATRIX
   - Prioritized recommendations with clear justification
   - Implementation roadmap with milestones
   - Success metrics and monitoring strategy
   - Team training and knowledge transfer needs

Focus on practical, actionable recommendations rather than theoretical perfection.

ARCHITECTURE REVIEW: E-COMMERCE MODERNIZATION

## CURRENT STATE ASSESSMENT
**Pain Points Identified:**
- Database bottlenecks during peak traffic (Black Friday: 90% CPU utilization)
- Deployment coupling: single component change requires full system deployment  
- Team scaling issues: 15 developers working on monolithic codebase
- Performance degradation: page load times increased 40% over 12 months

## SOLUTION OPTIONS ANALYSIS

### OPTION 1: Database Optimization + Caching (Quick Win)
**Timeline**: 2-3 months
**Complexity**: Low-Medium  
**Benefits**: 
- 60-70% performance improvement estimated
- Minimal architectural disruption
- Team familiarity with existing stack
**Trade-offs**: 
- Doesn't address deployment coupling
- Limited long-term scalability solution

### OPTION 2: Domain-Driven Microservices (Long-term Vision)  
**Timeline**: 12-18 months
**Complexity**: High
**Benefits**:
- Independent team scaling per service
- Technology diversity opportunities  
- Fault isolation and independent deployments
**Trade-offs**:
- Operational complexity increase (monitoring, distributed debugging)
- Network latency and data consistency challenges
- Significant team training requirements

### OPTION 3: Modular Monolith + Selective Extraction (Hybrid)
**Timeline**: 6-9 months  
**Complexity**: Medium
**Benefits**:
- Maintains monolith simplicity while enabling gradual extraction
- Clearer service boundaries identification before microservices transition
- Reduced risk compared to full microservices approach
**Trade-offs**:
- Still some deployment coupling initially
- Requires disciplined team boundaries enforcement

## RECOMMENDATION MATRIX

**RECOMMENDED APPROACH: Phased Hybrid Strategy**

**Phase 1 (Months 1-3): Performance Quick Wins**
- Implement database read replicas and query optimization
- Add Redis caching layer for hot data paths
- Estimated impact: 65% performance improvement

**Phase 2 (Months 4-9): Modular Monolith Refactoring**  
- Extract user management and payment processing as bounded contexts
- Implement internal API boundaries with clear contracts
- Prepare team structure alignment with domain boundaries

**Phase 3 (Months 10-15): Selective Microservices Extraction**
- Extract user service (highest team velocity impact)
- Extract payment service (compliance isolation benefits)
- Evaluate further extractions based on Phase 2 learnings

**SUCCESS METRICS:**
- Page load time: <2s (currently 4.5s)
- Deployment frequency: Daily (currently weekly)
- Developer velocity: 30% increase in story completion
- System availability: 99.9% uptime (currently 99.5%)