repository-pattern

The repository pattern for aggregate roots using EF Core is implemented by defining data access interfaces in the Domain layer and concrete implementations in the Infrastructure layer. This abstracts data access and provides a clean boundary around aggregate roots.

Yes, the repository pattern works with Unit of Work for EF Core by enabling coordinated SaveChanges across multiple repositories. The implementation ensures repositories contain no SaveChanges calls, delegating that responsibility to the Unit of Work.

Registering EF Core repositories with dependency injection involves providing interface definitions and concrete implementations to the DI container. The pattern includes DI registration support to wire up domain interfaces with their infrastructure implementations.

Yes, you can use specifications for complex queries with the repository pattern. The implementation supports optional specifications for advanced filtering, allowing you to encapsulate query logic and apply it across aggregate root repositories.

Repositories should not call SaveChanges in EF Core to maintain a coordinated data persistence boundary. By omitting SaveChanges calls, the repository pattern delegates transaction control to the Unit of Work, ensuring atomic saves across multiple aggregate roots.

Yes, you need CancellationToken support for EF Core repository implementations to allow cooperative cancellation of data access operations. The generated repository pattern ensures CancellationToken is supported throughout its interface definitions and concrete implementations.