Helpdesk Database Overview

Audience

Developers, database engineers, QA, support, security and architects.

Summary

Helpdesk Service owns canonical ticket persistence through a dedicated EF Core context. File bytes remain outside relational persistence; attachment rows retain external document/storage references.

Reference Content

The context owns ticket/reference records, child activity, SLA/escalation tracking, audit/timeline, processed events and outbox messages. Endpoint handlers and backfill tooling access the concrete context directly; no repository layer or secondary runtime context exists.

Canonical persistence is Foundation/Partial. Compatibility identifiers and backfill support make the storage model Transitional. Retention, concurrency and production migration procedures are not implemented in the reviewed source.

Requires confirmation

Authoritative ownership after cutover, production provider configuration, operational stewardship and recovery objectives require confirmation.

Source References

• microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.cs
• microservices/src/helpdesk-service/Domain/HelpdeskEntities.cs
• microservices/src/helpdesk-service/Infrastructure/Persistence.cs
• microservices/src/helpdesk-service/Program.cs

Related Articles

• Database overview
• Schema reference
• Database limitations

See Also

• API documentation
• Technical documentation

Keywords

Database overview, persistence ownership, canonical storage, compatibility.

Revision Information

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