事件溯源跨聚合约束：单账户仅运行一个AccountMaintainer的最优方案

针对你的账户维护任务并发约束问题，结合Eventuous、EventStoreDB和C#，可以采用短生命周期任务聚合+全局账户状态投影的纯事件溯源方案，既解决无限流问题，又避免时间分区的边界繁琐逻辑。

核心设计思路 #

将原有的AccountMaintainer长生命周期聚合拆分为短生命周期的AccountMaintenanceTask聚合，每个维护任务对应独立的事件流；同时通过EventStoreDB投影（或Eventuous订阅）维护一个**AccountMaintenanceStatus派生状态投影**，专门跟踪每个账户的当前活跃维护任务状态，以此实现单账户同一时间仅能运行一个维护任务的核心约束。

具体实现细节 #

1. 定义聚合与事件 #

// 维护任务聚合
public class AccountMaintenanceTask : Aggregate<AccountMaintenanceTaskState>
{
    public AccountMaintenanceTask() : base(AccountMaintenanceTaskState.Initial) { }

    public void Start(Guid accountId, DateTime timestamp)
    {
        Apply(new MaintenanceStarted(accountId, Id, timestamp));
    }

    public void Complete(DateTime timestamp)
    {
        Apply(new MaintenanceCompleted(State.AccountId, Id, timestamp));
    }
}

// 聚合状态
public record AccountMaintenanceTaskState : AggregateState<AccountMaintenanceTaskState>
{
    public Guid AccountId { get; private set; }
    public bool IsCompleted { get; private set; }

    public static AccountMaintenanceTaskState Initial => new();

    public AccountMaintenanceTaskState When(MaintenanceStarted e)
        => this with { AccountId = e.AccountId, IsCompleted = false };

    public AccountMaintenanceTaskState When(MaintenanceCompleted e)
        => this with { IsCompleted = true };
}

// 事件定义
public record MaintenanceStarted(Guid AccountId, Guid TaskId, DateTime Timestamp) : Event;
public record MaintenanceCompleted(Guid AccountId, Guid TaskId, DateTime Timestamp) : Event;

2. 实现账户状态投影 #

用Eventuous的订阅功能实现投影，维护每个账户的活跃任务ID：

public class AccountMaintenanceStatusProjection : Subscription<AccountMaintenanceStatus>
{
    public AccountMaintenanceStatusProjection(
        IEventStore eventStore,
        ICheckpointStore checkpointStore
    ) : base(eventStore, checkpointStore) { }

    public override async Task<AccountMaintenanceStatus> HandleEvent(
        IMessageConsumeContext context,
        AccountMaintenanceStatus state
    )
    {
        return context.Message switch
        {
            MaintenanceStarted e => state with
            {
                ActiveTaskId = e.TaskId
            },
            MaintenanceCompleted e => state with
            {
                ActiveTaskId = null
            },
            _ => state
        };
    }

    protected override string GetStreamName(Guid streamId)
        => $"AccountMaintenanceStatus-{streamId}"; // 每个账户对应一个投影流
}

// 投影状态
public record AccountMaintenanceStatus
{
    public Guid? ActiveTaskId { get; init; } = null;
    public static AccountMaintenanceStatus Empty => new();
}

3. 命令处理逻辑 #

在StartMaintenance命令处理中，先查询投影状态判断是否有活跃任务：

public class StartMaintenanceHandler : CommandHandler<StartMaintenance, AccountMaintenanceTask>
{
    private readonly IProjectionStore<AccountMaintenanceStatus> _projectionStore;

    public StartMaintenanceHandler(
        IAggregateStore aggregateStore,
        IProjectionStore<AccountMaintenanceStatus> projectionStore
    ) : base(aggregateStore)
    {
        _projectionStore = projectionStore;
    }

    public override async Task Execute(
        StartMaintenance command,
        CancellationToken cancellationToken
    )
    {
        // 查询账户当前维护状态
        var status = await _projectionStore.Load(
            command.AccountId,
            cancellationToken
        ) ?? AccountMaintenanceStatus.Empty;

        if (status.ActiveTaskId != null)
        {
            throw new InvalidOperationException(
                $"Account {command.AccountId} already has an active maintenance task ({status.ActiveTaskId})"
            );
        }

        // 创建新的维护任务聚合
        var taskId = Guid.NewGuid();
        var task = new AccountMaintenanceTask();
        task.Start(command.AccountId, command.Timestamp);

        await Store.Save(task, cancellationToken);
    }
}

// 命令定义
public record StartMaintenance(Guid AccountId, DateTime Timestamp) : Command;

方案优势 #

• 避免无限流问题：每个AccountMaintenanceTask聚合的事件流仅包含MaintenanceStarted和MaintenanceCompleted两个事件，生命周期结束后不再更新，无需快照；
• 消除时间分区边界逻辑：通过投影直接跟踪账户的实时活跃状态，无需跨日期检查多个流；
• 纯事件溯源合规：所有状态均由事件派生，仅依赖EventStoreDB，无需额外基础设施；
• 清晰的聚合边界：短生命周期聚合职责单一，符合DDD聚合设计原则，避免了“无限流聚合”的边界模糊问题。

关于动态一致性边界 #

这里的AccountMaintenanceStatus投影就是动态维护的一致性边界：它通过订阅所有维护任务事件，实时更新账户的活跃状态，确保命令处理时能获取到最新的约束状态。Eventuous的订阅机制会自动处理事件的顺序性，保证投影状态的最终一致性，同时在命令处理时可以通过投影的加载接口获取近乎实时的状态，满足业务约束的需求。

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