Helpdesk Application Layer

Audience

Developers, QA, support and architects.

Summary

The named Application folder is small: it defines tenant context and a domain-validation exception. Most use-case orchestration resides in static Minimal API handlers.

Reference Content

Handlers receive dependencies from endpoint injection, query the concrete DbContext, construct or mutate entities, append activity/outbox records and call SaveChanges. Private helpers implement ticket projection, required/trim validation, status date handling and lifecycle changes.

Document access is abstracted behind an interface. Persistence and ticket operations do not use application-service interfaces. Tenant/domain exceptions are mapped by service middleware; handlers also return explicit not-found, bad-request and dependency-unavailable results.

Requires confirmation

Whether handlers should be refactored into application services, transaction policies and a consistent error contract require confirmation.

Source References

• microservices/src/helpdesk-service/Application/Common.cs
• microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
• microservices/src/helpdesk-service/Infrastructure/DocumentServiceClient.cs

Related Articles

• Technical overview
• Technical limitations
• Helpdesk business documentation

See Also

• Technical source map
• Architecture overview

Keywords

Application layer, endpoint orchestration, dependency injection, error handling.

Revision Information

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