如何基于最佳实践为单个服务配置多套参数并按需调用？

一、调整配置结构 #

将appsettings.json中的数组格式改为键值对，便于通过客户端标识快速定位对应配置：

"MailConfigurations": {
  "Client1": {
    "DisplayName": "Client1",
    "From": "testclient1@gmail.com",
    "Password": "qwerty123",
    "Host": "smtp.gmail.com",
    "Port": 465,
    "UserName": "testclient1@gmail.com",
    "UseSSL": true,
    "UseStartTls": true
  },
  "Client2": {
    "DisplayName": "Client2",
    "From": "testclient2@gmail.com",
    "Password": "qwerty123",
    "Host": "smtp.gmail.com",
    "Port": 465,
    "UserName": "testclient2@gmail.com",
    "UseSSL": true,
    "UseStartTls": true
  }
}

二、修改MailService构造函数 #

移除IOptions<MailConfiguration>依赖，直接接收MailConfiguration实例，提升服务灵活性：

public class MailService : IMailService
{
    private readonly MailConfiguration _settings;

    public MailService(MailConfiguration settings)
    {
        _settings = settings;
    }

    public async Task<bool> SendAsync(MailData mailData, CancellationToken ct = default)
    {
        // 原有邮件发送逻辑
    }
}

三、实现DI友好的工厂类 #

创建工厂封装服务实例创建逻辑，依赖IServiceProvider而非直接new，保持DI容器的控制权：

public interface IMailServiceFactory
{
    IMailService GetMailService(string clientKey);
}

public class MailServiceFactory : IMailServiceFactory
{
    private readonly IServiceProvider _serviceProvider;
    private readonly IConfiguration _configuration;
    private readonly Dictionary<string, IMailService> _cachedServices = new();

    public MailServiceFactory(IServiceProvider serviceProvider, IConfiguration configuration)
    {
        _serviceProvider = serviceProvider;
        _configuration = configuration;
    }

    public IMailService GetMailService(string clientKey)
    {
        // 优先从缓存获取，避免重复创建实例
        if (_cachedServices.TryGetValue(clientKey, out var existingService))
        {
            return existingService;
        }

        // 读取对应客户端的配置节点
        var configSection = _configuration.GetSection($"MailConfigurations:{clientKey}");
        if (!configSection.Exists())
        {
            throw new ArgumentException($"未找到客户端[{clientKey}]的邮件配置");
        }

        var mailConfig = configSection.Get<MailConfiguration>() 
            ?? throw new InvalidOperationException($"加载客户端[{clientKey}]配置失败");

        // 通过容器创建MailService实例，保留DI能力（后续服务新增依赖无需修改工厂）
        var newService = ActivatorUtilities.CreateInstance<MailService>(_serviceProvider, mailConfig);
        
        _cachedServices.Add(clientKey, newService);
        return newService;
    }
}

四、注册服务到DI容器 #

在Program.cs中注册工厂和MailService，让容器管理实例生命周期：

// 注册邮件服务工厂
builder.Services.AddTransient<IMailServiceFactory, MailServiceFactory>();
// 注册MailService，告知容器如何创建该类型实例
builder.Services.AddTransient<MailService>();

五、使用示例 #

在业务代码中通过工厂获取对应客户端的邮件服务：

public class MailController : ControllerBase
{
    private readonly IMailServiceFactory _mailServiceFactory;

    public MailController(IMailServiceFactory mailServiceFactory)
    {
        _mailServiceFactory = mailServiceFactory;
    }

    [HttpPost("send")]
    public async Task<IActionResult> SendMail([FromQuery] string clientKey, [FromBody] MailData mailData)
    {
        var mailService = _mailServiceFactory.GetMailService(clientKey);
        var sendResult = await mailService.SendAsync(mailData);
        return Ok(sendResult);
    }
}

方案优势 #

• 完全遵循依赖注入原则，不直接new实例，保持容器对对象生命周期的控制
• 工厂封装实例创建逻辑，业务代码无需关心配置加载和服务实例化细节
• 缓存机制减少重复创建实例的开销（适用于无状态服务）
• 配置结构清晰，便于扩展更多客户端配置

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