software-architect

Software Architecture Design

Description

Provide system architecture design proposals, technology stack recommendations, and architecture tradeoff analysis to ensure solutions meet business requirements and non-functional requirements.

When to Use

• User requests "design architecture for XX system" or "help me choose tech stack"
• User asks about system scalability, high availability, or performance optimization strategies
• User needs microservices decomposition, module partitioning, or service boundary design
• User requests architecture review or refactoring proposal
• User asks how to apply architectural theories (CAP theorem, consistency models, distributed transactions) to specific scenarios
• User compares different architecture patterns or technology stacks

When NOT to Use

• User only needs specific code implementation or programming tips without architectural decisions
• User's problem is a pure algorithm or data structure implementation
• User needs UI/UX design rather than system architecture
• User only asks how to use a framework or library without system-level design
• User's project is extremely small (e.g., personal script, single-file tool) and doesn't require architecture

Input

{
  requirements: {
    businessScenario: string      // Business scenario description
    userScale?: string            // User scale (e.g., "1M DAU")
    qps?: string                  // Query/Request volume (e.g., "1000 QPS peak")
    dataVolume?: string           // Data volume (e.g., "10TB historical data")
    latencyRequirement?: string   // Latency requirement (e.g., "p99 < 100ms")
    readWriteRatio?: string       // Read/Write ratio (e.g., "read:write = 9:1")
    consistencyRequirement?: string // Consistency (strong/eventual/causal)
  }
  constraints: {
    budget?: string               // Budget constraints
    teamSize?: string             // Team size and skill set
    timeline?: string             // Delivery timeline
    existingTechStack?: string[]  // Existing technology stack
    complianceRequirements?: string // Compliance (e.g., GDPR, SOC2)
  }
  goals: {
    priority: string              // Core objective (performance/cost/time-to-market)
    tradeoffs?: string            // Known tradeoff preferences
  }
  existingArchitecture?: string   // Existing architecture (for review/refactoring)
}