+
-
- 客户端 (Web / App)
+ ↓ HTTP
+
+
+
-
+ {{ layer.name }}
+ {{ layer.badge }}
+ {{ layer.duty }}
- ⬇️ HTTP/HTTPS
-
+
+ ↓ SQL
+ 数据库 (MySQL / PostgreSQL)
-
-
-
-
-
-
-
-
-
- Controller
- 入口
-
-
-
-
- 职责：接收请求、参数校验、调用 Service
-
-
- 技术：Spring MVC / Gin / Echo
-
-
- ⬇️ 调用
-
-
-
-
-
-
-
-
- Service
- 业务核心
-
-
-
-
- 职责：业务逻辑编排、事务管理、跨模块协调
-
-
- 技术：纯代码逻辑 / 无框架依赖
-
-
- ⬇️ 调用
-
-
-
-
-
-
-
-
- Repository
- 数据访问
-
-
-
-
- 职责：数据持久化、查询封装、ORM 映射
-
-
- 技术：MyBatis / GORM / Hibernate
-
-
- ⬇️ SQL
-
-
-
-
-
-
-
-
- Domain / Model
- 领域模型
-
-
-
-
- 职责：实体定义、业务规则、值对象
-
-
- 技术：POJO / Struct / Class
-
-
- ⬇️ 持久化
-
-
-
-
-
-
-
- 数据库
-
-
- MySQL / PostgreSQL / MongoDB
-
-
-
diff --git a/docs/.vitepress/theme/components/appendix/backend-layered-architecture/RepositoryLayerDemo.vue b/docs/.vitepress/theme/components/appendix/backend-layered-architecture/RepositoryLayerDemo.vue
index 4d77e6f..0570b92 100644
--- a/docs/.vitepress/theme/components/appendix/backend-layered-architecture/RepositoryLayerDemo.vue
+++ b/docs/.vitepress/theme/components/appendix/backend-layered-architecture/RepositoryLayerDemo.vue
@@ -1,1064 +1,172 @@
- {{ layerInfo.title }}
-{{ layerInfo.description }}
-
- 💡 类比：{{ layerInfo.analogy }}
-
-
- ⚠️ 常见错误：
+
-
-
-
+
{{ activeInfo.title }}
+ {{ activeInfo.desc }}
+{{ activeInfo.analogy }}
+
+ 常见错误：
-
-
- - {{ mistake }} - +
- {{ m }}
- 💡 点击各层查看详细说明 | 实际调用流向：从上到下，依赖从下到上
-
-
-
🗄️ Repository 层：数据的"仓库管理员"
-- Repository 封装数据访问逻辑，让上层无需关心数据库细节 -
+
+
+
-
- Repository 层：数据的"仓库管理员"
+ Repository 封装数据访问逻辑，让上层无需关心数据库细节
-
-
-
-
-
+
+
+
+
+
+
+
+ {{ view === 'bad' ? '在 Service 里直接写 SQL' : '使用 Repository 封装数据访问' }}
+ {{ view === 'bad' ? '耦合严重' : '清晰解耦' }}
-
-
-
-
-
-
-
-
-
- 😫 在 Service 里直接写 SQL
- 耦合严重
-
+ {{ view === 'bad' ? badCode : goodCode }}@Service
-public class OrderService {
-
- @Autowired
- private JdbcTemplate jdbcTemplate; // 直接依赖底层 JDBC
-
- public List<Order> getUserOrders(Long userId) {
- // ❌ 问题1：SQL 硬编码在 Service 里
- // ❌ 问题2：更换数据库需要改业务代码
- // ❌ 问题3：无法单元测试，必须连真实数据库
- String sql = "SELECT * FROM orders WHERE user_id = ? AND deleted = 0";
-
- return jdbcTemplate.query(sql, (rs, rowNum) -> {
- Order order = new Order();
- order.setId(rs.getLong("id"));
- order.setUserId(rs.getLong("user_id"));
- order.setTotalAmount(rs.getBigDecimal("total_amount"));
- // ... 更多字段映射
- return order;
- }, userId);
- }
-
- public void updateOrderStatus(Long orderId, OrderStatus status) {
- // ❌ 问题4：到处重复 SQL 片段
- String sql = "UPDATE orders SET status = ?, updated_at = NOW() WHERE id = ?";
- jdbcTemplate.update(sql, status.name(), orderId);
- }
-}
-
-
- 😰 这种做法的问题
--
-
- 数据库耦合：业务代码里到处都是 SQL，换数据库等于重写 -
- 难以测试：Service 必须连真实数据库才能跑，单元测试变成集成测试 -
- 代码重复：同样的查询条件（如 deleted=0）在每个方法里重复写 -
- 安全隐患：手写 SQL 容易漏掉防注入处理 -
-
+
- 😊 使用 Repository 封装数据访问
- 清晰解耦
-
-
-
- // ========== 1. 实体定义（Domain） ==========
-@Entity
-@Table(name = "orders")
-public class Order {
- @Id
- @GeneratedValue(strategy = GenerationType.IDENTITY)
- private Long id;
-
- @Column(name = "user_id", nullable = false)
- private Long userId;
-
- @Column(name = "total_amount")
- private BigDecimal totalAmount;
-
- @Enumerated(EnumType.STRING)
- private OrderStatus status;
-
- @Column(name = "deleted")
- private Boolean deleted = false;
-
- // getters and setters...
-}
-
-// ========== 2. Repository 接口定义 ==========
-@Repository
-public interface OrderRepository extends JpaRepository<Order, Long> {
-
- // ✅ Spring Data 自动生成查询 - 简单查询
- List<Order> findByUserIdAndDeletedFalse(Long userId);
-
- // ✅ 自定义 JPQL 查询 - 复杂统计
- @Query("""
- SELECT new com.example.OrderStatistics(
- o.userId,
- COUNT(o),
- SUM(o.totalAmount),
- MAX(o.createdAt)
- )
- FROM Order o
- WHERE o.createdAt BETWEEN :startDate AND :endDate
- AND o.deleted = false
- GROUP BY o.userId
- HAVING COUNT(o) >= :minOrderCount
- ORDER BY SUM(o.totalAmount) DESC
- """)
- List<OrderStatistics> findUserOrderStatistics(
- @Param("startDate") LocalDateTime startDate,
- @Param("endDate") LocalDateTime endDate,
- @Param("minOrderCount") Long minOrderCount,
- Pageable pageable
- );
-
- // ✅ 批量更新 - 修改状态
- @Modifying
- @Query("UPDATE Order o SET o.status = :newStatus, " +
- "o.updatedAt = CURRENT_TIMESTAMP WHERE o.id IN :ids")
- int batchUpdateStatus(
- @Param("ids") List<Long> orderIds,
- @Param("newStatus") OrderStatus newStatus
- );
-}
-
-// ========== 3. Service 层（纯业务逻辑） ==========
-@Service
-public class OrderService {
-
- @Autowired
- private OrderRepository orderRepository; // ✅ 依赖接口，不依赖具体实现
-
- @Autowired
- private UserRepository userRepository;
-
- // ✅ 业务方法清晰简洁，不关心数据怎么存
- public List<OrderDTO> getUserOrders(Long userId) {
- // 可以在这里加业务校验
- User user = userRepository.findById(userId)
- .orElseThrow(() -> new UserNotFoundException(userId));
-
- // 直接调用 Repository，SQL 藏在后面
- List<Order> orders = orderRepository.findByUserIdAndDeletedFalse(userId);
-
- // 转换为 DTO 返回
- return orders.stream()
- .map(OrderDTO::from)
- .collect(Collectors.toList());
- }
-}
-
-
- 🎉 这样做的好处
--
-
- 关注点分离：Service 专注于业务，Repository 专注于数据，各管一摊 -
- 可测试性高：Service 只依赖 Repository 接口，单元测试可以用 Mock 对象替代真实数据库 -
- 代码复用：通用的查询方法（如 findByUserId）定义一次，到处复用 -
- 切换成本低：从 MySQL 换成 MongoDB，只需改 Repository 实现，Service 完全不动 -
+ {{ view === 'bad' ? '这种做法的问题' : '这样做的好处' }}
+
-
+
- {{ item }} +
-
diff --git a/docs/.vitepress/theme/components/appendix/backend-layered-architecture/ServiceLayerDemo.vue b/docs/.vitepress/theme/components/appendix/backend-layered-architecture/ServiceLayerDemo.vue
index 059479f..91d4680 100644
--- a/docs/.vitepress/theme/components/appendix/backend-layered-architecture/ServiceLayerDemo.vue
+++ b/docs/.vitepress/theme/components/appendix/backend-layered-architecture/ServiceLayerDemo.vue
@@ -1,123 +1,57 @@
- 📊 不同 Repository 实现方式对比
- -
-
+
-
-
-
- 实现方式
-
-
- 优点
-
-
- 缺点
-
-
- 适用场景
-
-
-
-
-
- Spring Data JPA
-
-
- 主流方案
-
-
-
- -
-
- 方法名自动推导查询 -
- 分页排序内置支持 -
- 事务管理集成 -
-
- -
-
- 复杂查询性能一般 -
- 学习曲线较陡 -
- 快速开发、标准 CRUD 业务
-
-
-
-
-
- MyBatis / MyBatis-Plus
-
-
- 国内主流
-
-
-
- -
-
- SQL 完全可控 -
- 复杂查询性能优 -
- 动态 SQL 强大 -
-
- -
-
- 需要手写 SQL -
- 样板代码较多 -
- 复杂查询、性能敏感业务
-
-
-
-
- Spring Data JDBC
-
-
- 轻量
-
-
-
- -
-
- 简单轻量 -
- 无延迟加载 -
- 启动快速 -
-
- -
-
- 无复杂映射 -
- 功能较简单 -
- 微服务、简单聚合根场景
-
-
+
+
+
不同 Repository 实现方式对比
+ | 实现方式 | 优点 | 缺点 | 适用场景 |
|---|---|---|---|
| {{ r.name }} {{ r.tag }} |
+ {{ r.pros }} | +{{ r.cons }} | +{{ r.scene }} | +
-
-
⚙️ Service 层：业务逻辑的"指挥家"
-- Service 层编排业务逻辑，协调多个 Repository，管理事务边界 -
+
+
+
-
- Service 层：业务逻辑的"指挥家"
+ 选择业务场景，查看 Service 层如何编排逻辑
-
- 选择业务场景：
-
-
+
+
-
-
-
- {{ currentScenarioData.title }}
- {{ currentScenarioData.description }}
-
+
+
{{ data.title }}
+ {{ data.desc }}
-
+
-
-
- {{ index + 1 }}
-
+
+ {{ i + 1 }}
-
-
-
-
+
- {{ step.name }}
-
-
- {{ step.layer }}
-
-
-
-
-
- {{ step.code }}
-
-
-
-
-
-
-
- {{ subStep.name }}
-
-
- {{ subStep.desc }}
-
-
- {{ subStep.statusText }}
+
{{ step.code }}
+
+
+
+
+ {{ sub.status }}
{{ sub.name }}
+ {{ sub.desc }}
-
🎯 Service 层设计原则
-
-
-
-
- {{ principle.title }}
-
-
- {{ principle.desc }}
-
-
-
+ {{ principle.example }}
-
+
@@ -127,8 +61,8 @@
diff --git a/docs/.vitepress/theme/components/appendix/computer-fundamentals/CompileVsInterpretDemo.vue b/docs/.vitepress/theme/components/appendix/computer-fundamentals/CompileVsInterpretDemo.vue
index 3a1da8a..6a57ec9 100644
--- a/docs/.vitepress/theme/components/appendix/computer-fundamentals/CompileVsInterpretDemo.vue
+++ b/docs/.vitepress/theme/components/appendix/computer-fundamentals/CompileVsInterpretDemo.vue
@@ -47,12 +47,17 @@
Service 层设计原则
+
+
+
{{ p.title }}
+ {{ p.desc }}
+ {{ p.example }}