Skip to main content

Performance Project Structure

Summary​

Source layout and responsibility map for the Performance service project.

Audience​

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

Overview​

The project is a single deployable web application with folder-based separation rather than separate assemblies for each internal layer.

Confirmed implementation​

  • Api contains minimal endpoint registration and result mapping.
  • Application contains commands, queries, DTO mappings, compatibility services, and integration ports.
  • Domain contains aggregate roots, entities, value objects, events, enums, and repository ports.
  • Infrastructure contains EF Core persistence, repository adapters, tenant context, audit/timeline adapters, and Workflow HTTP integration.
  • Messaging contains the outbox relay; Backfill contains migration and validation tooling.

Classification​

Implemented folder-based layering; physical assembly isolation is Not implemented.

Requires confirmation​

Whether layers will become separately compiled projects requires confirmation.

See Also​

Keywords​

  • Performance service
  • Project Structure
  • Draft technical documentation

Source References​

  • microservices/src/performance-service/performance-service.csproj
  • microservices/src/performance-service/Program.cs
  • microservices/src/performance-service/Domain
  • microservices/src/performance-service/Application
  • microservices/src/performance-service/Infrastructure
  • microservices/src/performance-service/Messaging
  • microservices/src/performance-service/Backfill

Revision Information​

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