Back to Details

system-design

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

System Design

系统设计

Help design systems and evaluate architectural decisions.
协助设计系统并评估架构决策。

Framework

框架

1. Requirements Gathering

1. 需求收集

  • Functional requirements (what it does)
  • Non-functional requirements (scale, latency, availability, cost)
  • Constraints (team size, timeline, existing tech stack)
  • 功能性需求（系统实现的功能）
  • 非功能性需求（规模、延迟、可用性、成本）
  • 约束条件（团队规模、时间线、现有技术栈）

2. High-Level Design

2. 高层设计

  • Component diagram
  • Data flow
  • API contracts
  • Storage choices
  • 组件图
  • 数据流
  • API契约
  • 存储选型

3. Deep Dive

3. 深入设计

  • Data model design
  • API endpoint design (REST, GraphQL, gRPC)
  • Caching strategy
  • Queue/event design
  • Error handling and retry logic
  • 数据模型设计
  • API端点设计（REST、GraphQL、gRPC）
  • 缓存策略
  • 队列/事件设计
  • 错误处理与重试逻辑

4. Scale and Reliability

4. 扩展性与可靠性

  • Load estimation
  • Horizontal vs. vertical scaling
  • Failover and redundancy
  • Monitoring and alerting
  • 负载估算
  • 横向扩展 vs 纵向扩展
  • 故障转移与冗余
  • 监控与告警

5. Trade-off Analysis

5. 权衡分析

  • Every decision has trade-offs. Make them explicit.
  • Consider: complexity, cost, team familiarity, time to market, maintainability
  • 每个决策都存在权衡，需明确说明。
  • 考量因素：复杂度、成本、团队熟悉度、上市时间、可维护性

Output

输出

Produce clear, structured design documents with diagrams (ASCII or described), explicit assumptions, and trade-off analysis. Always identify what you'd revisit as the system grows.
生成清晰、结构化的设计文档，包含图表（ASCII格式或文字描述）、明确的假设条件以及权衡分析。需始终指出随着系统增长需要重新审视的内容。