Helpdesk Persistence Architecture

Audience

Developers, database engineers, security, support and architects.

Summary

One context coordinates canonical relational state and outbox records. Document bytes are delegated outside the relational boundary.

Reference Content

Most lifecycle writes add domain changes, activity records and outbox rows before one SaveChanges call. External document upload occurs before that relational save and is not part of the transaction.

Requires confirmation

Distributed consistency, external-file compensation, provider resilience and persistence service-level objectives require confirmation.

Source References

• microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.cs
• microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
• microservices/src/helpdesk-service/Infrastructure/Persistence.cs
• microservices/src/helpdesk-service/Infrastructure/DocumentServiceClient.cs

Related Articles

• Database overview
• Schema reference
• Database limitations

See Also

• API documentation
• Technical documentation

Keywords

Persistence architecture, relational boundary, document storage, outbox.

Revision Information

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