architecture-design

System architecture design, module partitioning, code refactoring, and technology stack selection. Core contents: three-tier architecture guidelines, business module decomposition, table design standards, and technology-stack prioritization decisions. Trigger scenarios: - Overall system architecture design - Module decomposition and structural planning for new business modules - Code layering and refactoring strategies - Dependency analysis and decoupling - Recommendations for architecture evolution paths - Domain boundary delineation and package structure design - Technology stack selection and solution decision-making Trigger words: architecture design, module partitioning, three-layer architecture, layering, domain division, refactoring, decoupling, dependency management, system design, code organization, tech stack, architecture evolution Notes: 1. For specific technology comparisons (e.g., Redis vs local cache) -> use tech-decision 2. For development of specific CRUD modules -> use crud-development 3. For database table creation and dictionary configuration -> use database-ops 4. This project is purely backend (no frontend code)