Business Invariants are always satisfied

If an Aggregate object exists, it is already satisfying all Invariants and is, therefore, valid.

An Aggregate is the designated boundary within which all Invariants have to be satisfied.

• If the Aggregate is too small, satisfying invariants may mean touching more than one Aggregate, which is a bad practice #TODO: Add References
• If the Aggregate is too big, satisfying invariants will mean more chances of concurrency conflicts #TODO: Add References

Since an Aggregate can change at many interface points, validations that approve the state change are present within Aggregates.

The Domain rejects any change that violates invariants with a Domain Exception, halting program execution. The Exception would contain additional context about the violated invariant.