abp-entity-patterns

Design DDD entities by selecting appropriate ABP base classes like FullAuditedAggregateRoot for aggregate roots, applying IMultiTenant for multi-tenant support, and ISoftDelete for soft-delete behavior. This ensures entities handle auditing, tenancy, and deletion concerns while maintaining domain logic encapsulation within aggregate boundaries.

Generic repositories provide out-of-box CRUD operations for standard queries, while custom repositories extend them with domain-specific query logic. Use custom repositories when you need complex filtering, specialized business rules, or queries involving multiple aggregates to keep data access concerns separate from entities.

Create a domain service when business logic involves multiple entities, external domain concepts, or operations beyond a single aggregate's responsibility. Domain services keep entities focused on their own state while handling cross-aggregate orchestration, making logic reusable and testable.

Implement data seeding by creating seed data workflows that populate your entities with initial values using EF Core and ABP's data-seeding infrastructure. This ensures consistent baseline data across environments for testing, development, and production scenarios.

Yes, combine soft delete using ISoftDelete with auditing through FullAuditedAggregateRoot to track creation, modification timestamps, and user information while preserving deleted records. ABP handles both concerns through base classes, enabling audit trails for compliance without data loss.

Yes, ABP supports multi-tenancy at the entity level through the IMultiTenant interface, which adds tenant isolation automatically. This ensures each tenant's data remains segregated in the database while your repositories and domain services handle tenant context transparently.