domain-entity

You create C# domain entities using factory methods like Create that enforce validation, use private setters for encapsulation, and raise domain events for state changes. This ensures entities stay in valid states throughout their lifecycle.

Domain events in DDD represent state changes like Created, Updated, and Deactivated within domain entities. You use them to reflect invariant-protected state transitions, keeping behavior inside the entity rather than external services.

You structure aggregate roots with child entities and value objects using deterministic construction and encapsulation. Factory methods validate inputs, private setters protect invariants, and domain events track state changes across the aggregate.

Yes, this DDD pattern supports rich domain models where behavior lives in the entity rather than services. It applies encapsulation, factory methods, and domain events to maintain valid, behavior-rich models across aggregate roots and child entities.

The best way to protect invariants in C# domain entities is through encapsulation with private setters, factory methods with validation, and domain events. This approach ensures deterministic construction and prevents invalid state transitions.

You should avoid aggregate roots when your domain lacks complex invariants or child entity relationships. This pattern adds construction overhead and event-raising complexity that may not benefit simple CRUD models without behavior-rich requirements.