Since all objects contained by an aggregate share the same transactional boundary, performance and scalability issues may arise if an aggregate grows too large. The consistency of the data can be a convenient guiding principle for designing an aggregate’s boundaries. Only the information that is required by the aggregate’s business logic to be strongly consistent should be a part of the aggregate.
