事件源聚合根是否应该访问事件源库？

public class Person : AggregateRootBase
{
    private Guid? _bookingId;

    public Person(Identification identification)
    {
        Apply(new PersonCreatedEvent(identification));
    }

    public Booking CreateBooking() {
        // Enforce Person invariants
        var booking = new Booking();
        Apply(new PersonBookedEvent(booking.Id));
        return booking;
    }

    public void Release() {
        // Enforce Person invariants
        // Should we load the booking here from the aggregate repository?
        // We need to ensure that booking is released as well.
        var booking = BookingRepository.Load(_bookingId);
        booking.Release();
        Apply(new PersonReleasedEvent(_bookingId));
    }

    [EventHandler]
    public void Handle(PersonBookedEvent @event) { _bookingId = @event.BookingId; }

    [EventHandler]
    public void Handle(PersonReleasedEvent @event) { _bookingId = null; }
}

public class Booking : AggregateRootBase
{
    private DateTime _bookingDate;
    private DateTime? _releaseDate;

    public Booking()
    {
        //Enforce invariants
        Apply(new BookingCreatedEvent());
    }

    public void Release() 
    {
        //Enforce invariants
        Apply(new BookingReleasedEvent());
    }

    [EventHandler]
    public void Handle(BookingCreatedEvent @event) { _bookingDate = SystemTime.Now(); }
    [EventHandler]
    public void Handle(BookingReleasedEvent @event) { _releaseDate = SystemTime.Now(); }
    // Some other business activities unrelated to a person
}

到目前为止,由于我对DDD的理解,Person和Booking都是单独的聚合根源,原因有两个：

>有时,业务组件会将Booking对象与数据库分开. (即,由于信息不正确,已被释放的人之前的预订已被修改).
>每当需要更新预订时,不应该在人员和预订之间锁定争用.

另一个业务要求是,对于一个人来说,一次不能进行预订.因此,我担心在读取端查询查询数据库,因为那里可能存在一些不一致(由于使用CQRS并且具有最终一致的读取数据库).

是否允许聚合根通过id为对象查询事件源后备存储(根据需要延迟加载它们)？是否有任何其他实施途径更有意义？