abp-ddd

Inherit from AggregateRoot<TKey>, use private setters with behavior methods, and enforce invariants in the primary constructor. Accept the id as a parameter generated externally via IGuidGenerator, and include a protected parameterless constructor for ORM compatibility.

Create a custom repository only when you need query methods beyond simple CRUD, since the generic IRepository<T, TKey> covers basic operations. Define the interface in the Domain layer and the implementation in the data layer, and only for aggregate roots.

No, only aggregate roots should have repositories. Child entities must be accessed and modified through their aggregate root so business rules are enforced; creating child repositories bypasses invariants and breaks data consistency.

Local events via AddLocalEvent are handled within the same transaction and can access the full entity. Distributed events via AddDistributedEvent are handled asynchronously across modules or services and use ETOs (Event Transfer Objects) containing only serializable data.

Public setters create anemic entities where validation logic leaks into services. Rich domain models use private setters with methods like SetCount that enforce invariants, keeping business rules inside the entity where they belong.