Helpdesk Database Concurrency

Audience

Developers, database engineers, QA and architects.

Summary

No row-version, concurrency token or explicit optimistic-concurrency handling is configured.

Reference Content

Unique indexes provide final duplicate protection for selected identities, but handlers do not translate resulting persistence conflicts into domain responses.

Ticket number generation uses a tenant row count plus one, and compatibility identity generation uses current maximum plus one. Concurrent creation can calculate the same value before unique enforcement. Automatic escalation checks for existence before insert without a unique constraint, so concurrent checks can create duplicates.

Updates use load/mutate/save without expected-version checks or locking.

Requires confirmation

Concurrency strategy, retry/conflict contract, atomic identifier generation, escalation uniqueness and load-testing acceptance require confirmation.

Source References

• microservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.cs
• microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
• microservices/src/helpdesk-service/Domain/HelpdeskEntities.cs

Related Articles

• Database overview
• Schema reference
• Database limitations

See Also

• API documentation
• Technical documentation

Keywords

Concurrency token, optimistic concurrency, race condition, unique index.

Revision Information

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