Attendance Deployment and Startup

Summary

Deployment supplies a built .NET service artifact and approved runtime configuration; startup may migrate the Attendance schema before serving requests.

Audience

• DevOps/SRE, release engineers, service owners, and database owners

Startup flow

Post-deployment validation covers process health, tenant-scoped read, intended gateway route, a safe non-mutating dependency check, outbox backlog/error review, and Payroll lock-client error signals. Development seeding must not be treated as production initialization.

Rollback separates application/routing rollback from schema/data rollback. Reversing populated migrations or deleting data is not prescribed and requires database-owner approval and evidence.

Source References

• microservices/src/attendance-service/attendance-service.csproj
• microservices/src/attendance-service/Dockerfile
• microservices/src/attendance-service/Program.cs
• microservices/src/attendance-service/Infrastructure/DevelopmentSeeder.cs

Related Articles

• Attendance operations
• Attendance troubleshooting
• Attendance technical documentation

See Also

• Attendance database documentation
• Attendance events documentation

Keywords

• Attendance operations
• Support
• Reliability

Revision Information

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