Helpdesk Database Limitations
Audience
Developers, product, database engineers, QA, security, support and architects.
Summary
Helpdesk persistence is Transitional. The following gaps are source-verified.
Reference Content
Persistence
- Direct DbContext access couples handlers and backfill to EF Core.
- Several logical identifiers have no relational foreign keys.
- External file bytes and relational metadata have no shared transaction.
Concurrency
- No concurrency tokens or conflict handling.
- Count/max-based identities and check-before-insert escalation are race-prone.
Tenant isolation
- Outbox and processed-event sets lack tenant global filters.
- Missing tenant reads generally scope to tenant zero instead of explicit rejection.
- Employee history is tenant-scoped, not requester-scoped.
Transactions
- No explicit transaction/isolation policy or distributed compensation.
- Outbox status updates save separately from original domain writes.
Compatibility
- Canonical and compatibility identity/metadata coexist.
- Backfill parity is aggregate, not field-complete.
- Compatibility-created reference data can expand tenant taxonomy.
Testing
- No dedicated mapping, migration, repository or database integration tests found.
Governance
- Production migration, backup, restore, indexing and ownership procedures are absent from source.
- Development startup can apply migrations and seed examples.
Retention
- No cleanup/archive/legal-hold behavior for tickets, activity, outbox or processed events.
- Local attachment-reference deletion does not delete the external document.
Requires confirmation
Release blockers, risk ownership, referential strategy, migration governance, retention and compatibility exit criteria require confirmation.
Source References
microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.csmicroservices/src/helpdesk-service/Api/HelpdeskEndpoints.csmicroservices/src/helpdesk-service/Infrastructure/Persistence.csmicroservices/src/helpdesk-service/Backfill/HelpdeskBackfill.csmicroservices/src/helpdesk-service/Infrastructure/DevelopmentSeeder.cs
Related Articles
See Also
Keywords
Database limitations, concurrency gap, tenant gap, retention gap.
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20