architecture
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseArchitecture Decision Framework
架构决策框架
"Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale."
"需求驱动架构，权衡影响决策，ADR记录决策依据。"
🎯 Selective Reading Rule
🎯 选择性阅读规则
Read ONLY files relevant to the request! Check the content map, find what you need.
| File | Description | When to Read |
|---|---|---|
| Questions to ask, project classification | Starting architecture design |
| ADR templates, trade-off framework | Documenting decisions |
| Decision trees, anti-patterns | Choosing patterns |
| MVP, SaaS, Enterprise examples | Reference implementations |
| Quick lookup for patterns | Pattern comparison |
仅阅读与请求相关的文件！ 查看内容地图，找到你需要的部分。
| 文件 | 描述 | 阅读时机 |
|---|---|---|
| 待问问题、项目分类 | 开始架构设计时 |
| ADR模板、权衡框架 | 记录决策时 |
| 决策树、反模式 | 选择模式时 |
| MVP、SaaS、企业级示例 | 参考实现时 |
| 模式快速查询 | 模式对比时 |
🔗 Related Skills
🔗 相关技能
| Skill | Use For |
|---|---|
| Database schema design |
| API design patterns |
| Deployment architecture |
| 技能 | 适用场景 |
|---|---|
| 数据库 schema 设计 |
| API 设计模式 |
| 部署架构 |
Core Principle
核心原则
"Simplicity is the ultimate sophistication."
- Start simple
- Add complexity ONLY when proven necessary
- You can always add patterns later
- Removing complexity is MUCH harder than adding it
"简单是终极的复杂。"
- 从简单开始
- 仅在被证明必要时才增加复杂度
- 你总能在之后添加模式
- 移除复杂度比添加它难得多
Validation Checklist
验证清单
Before finalizing architecture:
- Requirements clearly understood
- Constraints identified
- Each decision has trade-off analysis
- Simpler alternatives considered
- ADRs written for significant decisions
- Team expertise matches chosen patterns
在最终确定架构之前：
- 已明确理解需求
- 已识别约束条件
- 每个决策都有权衡分析
- 已考虑更简单的替代方案
- 已为重要决策编写ADR
- 团队能力与所选模式匹配