Prompt

You are a senior software architect conducting a comprehensive architecture review and design for [PROJECT/SYSTEM_NAME].

Create a detailed software architecture analysis and recommendations:

## Current Architecture Assessment

**System Overview:**
- Application type: [Web app, mobile app, enterprise system, microservices]
- Technology stack: [Languages, frameworks, databases, infrastructure]
- User base: [Number of users, usage patterns, growth projections]
- Performance requirements: [Response time, throughput, availability]
- Integration points: [External APIs, databases, services, legacy systems]

**Architecture Analysis:**
- Architectural style: [Monolithic, microservices, serverless, hybrid]
- Design patterns used: [MVC, Repository, Factory, Observer, etc.]
- Data flow: [Request processing, data storage, caching, synchronization]
- Security implementation: [Authentication, authorization, encryption, validation]
- Scalability approach: [Horizontal, vertical, auto-scaling, load balancing]

**Technical Debt Assessment:**
- Code quality issues: [Complexity, maintainability, test coverage]
- Performance bottlenecks: [Slow queries, inefficient algorithms, resource usage]
- Security vulnerabilities: [Known issues, compliance gaps, threat exposure]
- Outdated dependencies: [Legacy frameworks, unsupported libraries]
- Documentation gaps: [Missing specs, outdated docs, knowledge silos]

## Architecture Design & Recommendations

**Target Architecture:**
- Recommended architectural style: [Rationale for choice]
- Core components and services: [Detailed component breakdown]
- Data architecture: [Storage strategy, data flow, consistency model]
- Integration architecture: [API design, event-driven patterns, messaging]
- Infrastructure architecture: [Cloud strategy, containers, orchestration]

**System Components:**

**Application Layer:**
- Frontend: [Technology, framework, architecture pattern]
- Backend services: [API design, business logic, service boundaries]
- Data access layer: [ORM, repository pattern, caching strategy]
- Integration layer: [API gateway, service mesh, message brokers]

**Data Layer:**
- Database design: [Schema, indexing, partitioning, replication]
- Caching strategy: [Redis, CDN, application-level caching]
- Data pipeline: [ETL/ELT, real-time processing, analytics]
- Backup and recovery: [Strategy, RTO/RPO, testing procedures]

**Infrastructure Layer:**
- Deployment architecture: [Containers, orchestration, CI/CD]
- Security architecture: [Network security, encryption, identity management]
- Monitoring and observability: [Logging, metrics, tracing, alerting]
- Disaster recovery: [Multi-region, failover, backup strategies]

## Design Patterns & Best Practices

**Recommended Design Patterns:**
- Creational patterns: [Singleton, Factory, Builder applications]
- Structural patterns: [Adapter, Facade, Decorator usage]
- Behavioral patterns: [Observer, Strategy, Command implementation]
- Architectural patterns: [CQRS, Event Sourcing, Saga pattern]

**Development Principles:**
- SOLID principles application
- Domain-driven design (DDD) implementation
- Test-driven development (TDD) approach
- Clean architecture principles
- Microservices best practices

**Code Quality Standards:**
- Coding conventions: [Style guides, naming conventions, documentation]
- Testing strategy: [Unit, integration, end-to-end, performance testing]
- Code review process: [Guidelines, tools, quality gates]
- Static analysis: [Linting, security scanning, complexity analysis]

## Implementation Strategy & Success Metrics

**Implementation Phases:**
- Phase 1: Foundation (Months 1-3) - Infrastructure setup and core services
- Phase 2: Core Features (Months 4-6) - Business logic and API development
- Phase 3: Advanced Features (Months 7-9) - Performance optimization and monitoring
- Phase 4: Production Readiness (Months 10-12) - Security, documentation, deployment

**Success Metrics:**
- Performance: [Response time < Xms, throughput > Y req/sec]
- Reliability: [Uptime > 99.9%, error rate < 0.1%]
- Scalability: [Handle X concurrent users, Y transactions/sec]
- Security: [Zero critical vulnerabilities, compliance scores]
- Code Quality: [> 80% test coverage, maintainability index > X]

Include specific technology recommendations, implementation details, and measurable success criteria.