abp-entity-patterns

Choosing an ABP entity base class depends on your domain modeling needs for auditing, deletion, and multi-tenancy. You select from Entity, AuditedEntity, FullAuditedEntity, AggregateRoot, and FullAuditedAggregateRoot to enforce clean architecture boundaries.

Structuring custom repositories in ABP involves using EF Core repository templates to expose domain-focused queries. This approach preserves DDD boundaries while allowing scalable data access and consistent domain modeling across ABP-based project modules.

Idempotent data seeding in ABP uses the DataSeedContributor pattern to bootstrap consistent test and demo data. This ensures scalable data initialization across modules without duplicating records during application startup.

Use a domain service in ABP when you need to encapsulate cross-entity business rules that do not naturally belong to a single entity. DomainService components maintain clean architecture by keeping domain logic centralized and reusable.

ABP framework supports multi-tenancy with aggregate roots through the FullAuditedAggregateRoot base class. This provides built-in auditing, soft deletion, and multi-tenancy support for scalable domain modeling.

Scaffolding an ABP module with DDD patterns involves creating an example entity, custom EF Core repository, domain service, and data seeding contributor. This enforces consistent domain modeling and explicit repository boundaries.