Helpdesk Persistence Boundaries

Audience

Developers, database reviewers, QA, support and architects.

Summary

HelpdeskDbContext owns canonical helpdesk entities, activity records, processed-event state and outbox messages in a dedicated schema. PostgreSQL EF Core migrations define the current evolution.

Reference Content

Tenant entities share keys, tenant indexes and global filters. Ticket mappings define unique tenant/number and compatibility indexes plus requester, assignee and status indexes. Child collections cascade with Ticket deletion. Activity JSON and outbox payloads use structured storage types.

Command handlers generally commit domain changes, activity records and outbox messages through one DbContext SaveChanges call. External document calls are outside that relational unit of work. The outbox store selects Pending or Failed messages and marks them processed/failed.

Requires confirmation

Backup/retention, migration rollout, concurrency tokens, transaction isolation, outbox cleanup and external-file compensation require confirmation.

Source References

• microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.cs
• microservices/src/helpdesk-service/Infrastructure/Persistence.cs
• microservices/src/helpdesk-service/Infrastructure/Migrations/20260708165325_InitialHelpdeskSchema.cs
• microservices/src/helpdesk-service/Infrastructure/Migrations/20260709095325_AddHelpdeskDocumentAttachmentReferences.cs
• microservices/src/helpdesk-service/Infrastructure/Migrations/20260709105542_AddHelpdeskCompatFields.cs

Related Articles

• Technical overview
• Technical limitations
• Helpdesk business documentation

See Also

• Technical source map
• Architecture overview

Keywords

Helpdesk persistence, EF Core, migrations, indexes, transactional outbox.

Revision Information

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