abp-framework-patterns

To structure a domain-driven design application with ABP Framework, standardize repository, unit of work, domain service, and application service patterns across your modules. This approach ensures clean separation between domain, application, and infrastructure layers for maintainable apps.

Scaffolding a new ABP module involves generating a cohesive skeleton with entities, application services, DTOs, validators, and permissions. You create Domain, Application, and Infrastructure layers, then integrate EF Core and ABP permissions using the provided pattern templates.

The standard ABP patterns for multi-tenancy and distributed events enforce consistent infrastructure governance across modules. They provide standardized templates for managing tenant isolation and handling asynchronous background jobs and distributed event integration.

Yes, ABP Framework works with EF Core and Mapperly for data access and object mapping. The patterns include integration points for EF Core database contexts and Mapperly mappings to ensure consistent data flow across application layers.

You should use the unit of work pattern in ABP applications to manage transactional boundaries and ensure data consistency across repository operations. It standardizes transaction execution within domain services and application services.

The best way to implement authorization in an ABP application service is by applying the framework's standardized permission templates. This pattern integrates seamlessly with ABP's permission management system to enforce governance across module endpoints.