Repositories and Persistence

Summary

Repository, unit-of-work, EF Core, and PostgreSQL implementation.

Audience

Engineers, architects, QA, support, security reviewers, and operators working with the Performance module.

Overview

Domain repository interfaces expose aggregate load, add, remove, and query operations. EF Core adapters implement them over PerformanceDbContext, and UnitOfWork delegates to the context save operation.

Confirmed implementation

• Review-cycle lookup is tenant-filtered through the context.
• Appraisal aggregate loads include goals and reviews for command execution.
• Queryable access supports read-side filtering and reporting.
• PostgreSQL is the configured EF Core provider.
• Save translates domain events to outbox records before the database commit.

Classification

Implemented repository/unit-of-work pattern; generic repositories are Not implemented.

Requires confirmation

Optimistic concurrency policy, transaction isolation, archival, and repository query governance require confirmation.

Related Articles

• Performance technical documentation
• Performance module

See Also

• Technical known limitations
• Performance business documentation

Keywords

• Performance service
• Repositories and Persistence
• Draft technical documentation

Source References

• microservices/src/performance-service/Domain/Repositories.cs
• microservices/src/performance-service/Infrastructure/Persistence.cs
• microservices/src/performance-service/Infrastructure/PerformanceDbContext.cs
• microservices/src/performance-service/performance-service.csproj

Revision Information

• Status: Draft
• Last reviewed: 2026-07-16
• Review cycle: Quarterly