Skip to main content

Leave Readiness Storage

Audience​

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

Reference Content​

Summary​

Leave Service consumes Employee lifecycle information into a local EmployeeProfile. LeavePolicies and LeaveBalances are separate local records; automatic initial balance creation was not proven.

Projection and setup​

Selected objects​

  • EmployeeProfiles hold the leave-local employee projection and synchronization fields.
  • LeavePolicies define leave-side policy records.
  • LeaveBalances store balance state by employee and leave category/policy context.

Consistency​

The employee projection is eventually consistent with Employee Service. The Leave context has an outbox in its broader model but no selected processed-event object set in the context; consumer idempotency behavior should be verified end to end.

Not proven​

Policy assignment, balance initialization, carry-forward behavior and deactivation on exit are not established as automatic onboarding/offboarding consequences.

Requires confirmation​

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

Source References​

  • microservices/src/leave-service/Infrastructure/LeaveDbContext.cs
  • microservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs

See Also​

Keywords​

  • Onboarding database
  • Offboarding database
  • Lifecycle persistence

Revision Information​

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