Skip to main content

Helpdesk Runtime Composition

Audience​

Developers, DevOps, support, security and architects.

Summary​

Startup registers observability, shared messaging, tenant context, EF Core, the outbox store, a typed document client, API discovery, Swagger and health checks. Development startup can apply migrations and seed examples.

Reference Content​

Request pipeline​

Correlation runs before endpoint execution. A local exception middleware maps tenant-context and domain-validation failures to client errors. Swagger is mapped in the reviewed service without an environment guard.

Hosted behavior​

The source registers messaging and an outbox store, but this project does not visibly register a Helpdesk-specific background SLA checker. SLA checking is an explicit operation.

Requires confirmation​

Deployment environment, migration policy, Swagger exposure, outbox dispatcher activation and SLA-check scheduling require confirmation.

Source References​

  • microservices/src/helpdesk-service/Program.cs
  • microservices/src/helpdesk-service/Infrastructure/DocumentServiceClient.cs
  • microservices/src/helpdesk-service/Infrastructure/Persistence.cs
  • microservices/src/helpdesk-service/Infrastructure/DevelopmentSeeder.cs

See Also​

Keywords​

Runtime composition, dependency injection, middleware, startup, health checks.

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20