Skip to main content

Employment and Status Storage

Audience​

Developers, QA and support engineers, data reviewers, implementation partners, solution architects, privacy reviewers and security reviewers.

Reference Content​

Summary​

Employee Service stores employment details as an owned value within Employee and persists employee status as text. Compatibility HR Operations maintains separate workforce and login state.

Extracted state​

Confirmed Employee states are Active, On Leave, Suspended and Terminated. The mapping uses a string conversion, preserving readable model values but requiring controlled enum evolution. Employment details are owned by Employee and share its lifecycle.

Status propagation​

Boundary​

The extracted status and compatibility workforce status are not database-synchronized. A successful write in one store does not establish the other store's status.

Data integrity​

Tenant/status indexing supports scoped lists. No optimistic concurrency token was found on Employee, so simultaneous lifecycle commands depend on application validation and database constraints rather than row-version checks.

Requires confirmation​

Unless explicitly confirmed above, production migration governance, rollback, reconciliation, retention, privacy, performance, concurrency and operational ownership require confirmation.

Source References​

  • microservices/src/employee-service/Infrastructure/EmployeeDbContext.cs
  • microservices/src/employee-service/Domain/Employees/Employee.cs

See Also​

Keywords​

  • Onboarding database
  • Offboarding database
  • Lifecycle persistence

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Review cycle: Quarterly