Skip to main content

Performance Service Architecture

Summary​

Source-backed architecture of the standalone Performance bounded-context service.

Audience​

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

Overview​

Performance is an ASP.NET Core 8 minimal-API service. It organizes code into API, Application, Domain, Infrastructure, Messaging, and Backfill areas, references Shared Kernel and Contracts projects, persists through EF Core with PostgreSQL, and publishes lifecycle signals through a transactional outbox.

Confirmed implementation​

  • Gateway routing fronts native and compatibility traffic during a controlled transition.
  • Minimal API endpoint modules call scoped command, query, report, and compatibility services.
  • Application code depends on domain repository and unit-of-work ports; infrastructure supplies EF Core adapters.
  • Domain events are converted to shared integration contracts during the same save that persists aggregate changes.
  • Workflow is an optional synchronous integration; notification handling is downstream of messaging.

Classification​

Transitional because native and compatibility routing coexist and endpoint authorization is not enforced.

Requires confirmation​

Gateway cutover ownership, production service boundaries, authorization policy, and compatibility retirement require confirmation.

Diagram​

Runtime request flow​

See Also​

Keywords​

  • Performance service
  • Architecture
  • Draft technical documentation

Source References​

  • microservices/src/performance-service/performance-service.csproj
  • microservices/src/performance-service/Program.cs
  • microservices/src/performance-service/Infrastructure/PerformanceDbContext.cs
  • microservices/src/gateway-api/Program.cs

Revision Information​

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