Database Overview
Audience
Developers, database engineers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.
Reference Content
This page records source-verified Workforce Scheduling persistence behavior and boundaries.
Summary
The canonical scheduling foundation is persisted by Attendance Service. It stores shifts, employee assignments, tenant weekday rules, policies and rules, plus configuration audit/timeline evidence. Holiday persistence is outside that canonical slice.
Ownership
| Boundary | Verified role | Maturity |
|---|---|---|
| Attendance runtime context | Canonical shifts, assignments, weekly-off rules, attendance policies | Foundation/Partial |
| Leave runtime context | Leave-owned holidays and weekly-off calendar | Transitional adjacent owner |
| Monolith runtime context | Legacy shifts, holidays, weekly offs, and employee shift reference | Transitional fallback/source |
| Backfill context | Writes canonical entities while preserving compatibility identity | Transitional migration tool |
System of record
The code supports gateway-controlled ownership, so production authority cannot be inferred from source alone. Canonical model ownership is Attendance Service; runtime cutover state requires confirmation.
Exclusions
Attendance records, punches, payroll snapshots, leave requests, and unrelated context entities are outside the schema total except where they explain an integration boundary.
Source References
microservices/src/attendance-service/Infrastructure/AttendanceDbContext.csmicroservices/src/leave-service/Infrastructure/LeaveDbContext.csData/AppDbContext.csmicroservices/src/attendance-service/Backfill/ShiftPolicyBackfillTypes.cs
Related Articles
See Also
Keywords
- Workforce Scheduling database
- Shift persistence
- Attendance policy storage
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20