Skip to main content

Performance Layered Architecture

Summary​

Dependency direction across the source-backed Performance layers.

Audience​

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

Overview​

Endpoints depend on application services. Application services depend on domain types and ports. Infrastructure implements those ports and is composed at startup. Because the layers share one project, these boundaries are conventions enforced by source organization rather than assembly references.

Confirmed implementation​

  • Domain contains no EF Core dependency in aggregate behavior.
  • Repository and unit-of-work abstractions face inward from Application/Domain.
  • Infrastructure references domain and application abstractions to implement adapters.
  • Program is the composition root and knows every concrete adapter.

Classification​

Implemented as folder boundaries; compile-time layer isolation is Not implemented.

Requires confirmation​

Automated architecture tests and stricter dependency enforcement require confirmation.

Diagram​

See Also​

Keywords​

  • Performance service
  • Layered Architecture
  • Draft technical documentation

Source References​

  • microservices/src/performance-service/Program.cs
  • microservices/src/performance-service/Application/Common/Abstractions.cs
  • microservices/src/performance-service/Domain/Repositories.cs
  • microservices/src/performance-service/Infrastructure/Persistence.cs

Revision Information​

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