Skip to main content

Holiday Storage

Summary​

Holidays stores tenant-scoped calendar dates, names, and a paid/unpaid classification string.

Audience​

Backend developers, QA, architects, Leave/Attendance owners, and support.

Reference Content​

These are calculation relationships, not foreign keys. Holidays has an integer primary key, required bounded name/type, tenant filter, and non-unique tenant/date index. Multiple rows on the same tenant/date are database-permitted. No region, optional-calendar, active, or employee scope exists.

Create, update, and delete are tracked through application commands and audit entries. LeaveDayCalculator consumes Holiday dates only when the resolved active policy enables Holiday exclusion. Paid/unpaid is stored classification metadata; no database constraint restricts the string values and no calculation in this model derives pay. Compatibility with monolith Holidays remains Transitional.

Source References​

  • microservices/src/leave-service/Domain/Leave/CalendarEntities.cs
  • microservices/src/leave-service/Domain/Leave/LeaveDayCalculator.cs
  • microservices/src/leave-service/Infrastructure/LeaveDbContext.cs
  • microservices/src/leave-service/Application/LeaveWorkflows.cs

See Also​

Keywords​

  • Holiday storage
  • Leave calendar
  • Paid classification

Revision Information​

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