Helpdesk Architecture Overview
Audience
Developers, architects, QA, security and support engineers.
Summary
The extracted capability is one executable service with API, Application, Domain, Infrastructure and Backfill folders. Minimal API handlers directly coordinate EF Core and infrastructure clients; no independent application-service or repository assembly exists.
Reference Content
Boundaries
The executable owns helpdesk records and report projections. Shared Kernel supplies tenant base types, messaging/outbox and observability extensions. Contracts supplies lifecycle-event types. Gateway, Notification Service and Document Service are separate runtime boundaries.
Maturity
The architecture is Transitional because canonical and compatibility routes coexist, endpoint handlers contain most orchestration, and direct service authentication/authorization is not configured in the reviewed bootstrap.
Requires confirmation
Production topology, network controls, service ownership, event dispatcher hosting and the target post-compatibility architecture require confirmation.
Source References
microservices/src/helpdesk-service/Program.csmicroservices/src/helpdesk-service/helpdesk-service.csprojmicroservices/src/helpdesk-service/Api/HelpdeskEndpoints.csmicroservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.csmicroservices/src/gateway-api/Program.cs
Related Articles
See Also
Keywords
Helpdesk architecture, Minimal API, service boundary, EF Core, outbox.
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20