Node.js+MongoDB三层架构优化求助：如何实现松耦合？

你的代码目前的核心问题是各层直接绑定具体类，而非依赖抽象契约，导致层级间耦合过紧——比如Controller硬依赖Service类，Service硬依赖DAL类，后续要替换实现（比如换个DAL做测试、扩展Service逻辑）时，必须修改上层代码，灵活性很差。要实现松耦合，关键是遵循依赖倒置原则：依赖抽象而非具体实现。

具体优化步骤 #

1. 先定义抽象接口 #

为Service和DAL层定义接口，明确各层的功能契约，让上层只关心“做什么”，不关心“怎么做”：

// interfaces.ts
export interface IArticleDAL {
  searchByKeyword(keyword: string): Promise<any>;
}

export interface IArticleService {
  searchByKeyword(keyword: string): Promise<any>;
}

2. 改造各层实现类 #

让具体类实现对应的接口，把依赖从具体类换成抽象接口：

// controller.ts
import { IArticleService } from './interfaces';

export class Controller {
  private articleService: IArticleService;

  constructor(articleService: IArticleService) {
    this.articleService = articleService;
  }

  async searchByKeyword(keyword: string) {
    return await this.articleService.searchByKeyword(keyword);
  }
}

// service.ts
import { IArticleService } from './interfaces';
import { IArticleDAL } from './interfaces';

export class ArticleService implements IArticleService {
  private articlesDAL: IArticleDAL;

  constructor(articlesDAL: IArticleDAL) {
    this.articlesDAL = articlesDAL;
  }

  async searchByKeyword(keyword: string) {
    return await this.articlesDAL.searchByKeyword(keyword);
  }
}

// dal.ts
import { IArticleDAL } from './interfaces';
import { ArticleModel } from './your-model-path';

export class ArticleDAL implements IArticleDAL {
  async searchByKeyword(keyword: string) {
    return await ArticleModel.searchFullText(keyword);
  }
}

3. 优化实例创建逻辑 #

在路由中，我们依然可以手动创建实例，但此时上层依赖的是接口——后续如果要替换DAL或Service的实现，只需要新写一个类实现对应接口，完全不用修改Controller或路由代码：

// route.ts
import { Request, Response } from 'express';
import { Controller } from './controller';
import { ArticleService } from './service';
import { ArticleDAL } from './dal';
import { IArticleService, IArticleDAL } from './interfaces';

route.get("/", async (req: Request, res: Response) => {
  // 这里绑定具体实现，但上层依赖的是接口
  const articleDal: IArticleDAL = new ArticleDAL();
  const articleService: IArticleService = new ArticleService(articleDal);
  const articleController = new Controller(articleService);
  
  const { keyword } = req.query;
  const result = await articleController.searchByKeyword(keyword as string);

  res.json(result); // 用res.json比手动stringify更优雅
});

4. 可选：用依赖注入工具进一步解耦 #

如果项目规模较大，推荐用tsyringe或awilix这类DI工具自动管理依赖，彻底摆脱手动创建实例的繁琐：

以tsyringe为例：

// 先注册依赖（比如在项目入口文件）
import { container } from 'tsyringe';
import { IArticleDAL } from './interfaces';
import { ArticleDAL } from './dal';
import { IArticleService } from './interfaces';
import { ArticleService } from './service';

container.register<IArticleDAL>('IArticleDAL', { useClass: ArticleDAL });
container.register<IArticleService>('IArticleService', { useClass: ArticleService });

// 改造Controller，添加注入装饰器
import { injectable, inject } from 'tsyringe';

@injectable()
export class Controller {
  constructor(@inject('IArticleService') private articleService: IArticleService) {}

  async searchByKeyword(keyword: string) {
    return await this.articleService.searchByKeyword(keyword);
  }
}

// 路由中直接获取实例
route.get("/", async (req: Request, res: Response) => {
  const articleController = container.resolve(Controller);
  const { keyword } = req.query;
  const result = await articleController.searchByKeyword(keyword as string);

  res.json(result);
});

优化后的好处 #

• 松耦合：各层依赖抽象接口，替换具体实现（比如Mock DAL做单元测试）无需修改上层代码
• 可测试性：单元测试时可以轻松Mock接口实现，不用依赖真实数据库
• 扩展性：新增功能时，只需要实现对应接口即可，不会影响现有代码逻辑

内容的提问来源于stack exchange，提问作者Nghi Nguyen