Skip to main content

Attendance Technical Overview

Summary​

Attendance Service is a .NET 8 ASP.NET Core bounded-context service for attendance records, punches, calculation, Time Office configuration, review workflows, employee attendance profiles, payroll snapshots, and attendance integration-event production.

Audience​

  • Backend and frontend developers
  • QA, DevOps, support, security, and solution-architecture teams

Overview​

Technical scope and responsibility​

The service uses minimal API presentation, directly injected application services, domain aggregates and services, EF Core persistence backed by PostgreSQL, shared authentication and observability infrastructure, and a transactional outbox. It does not use MediatR. The gateway controls whether compatible attendance and Time Office traffic is served by the monolith or Attendance Service.

Architectural areas​

  • Api: presentation and compatibility adapters
  • Application: commands, queries, workflows, DTO mapping, validation, and ports
  • Domain: attendance and Time Office models, invariants, calculation, repository ports, and domain events
  • Infrastructure: persistence adapters, tenant filters, audit/timeline writers, outbox store and relay, and Payroll lock client
  • Backfill: migration and parity-support tooling for transitional Time Office ownership
  • Program.cs: composition root, middleware, security, health, migrations, and endpoint mapping

Dependencies and maturity​

The service references the Shared Kernel and Contracts projects. It depends conceptually on authenticated tenant context, an employee-profile projection, PostgreSQL, the event broker, the gateway, and Payroll lock state. Leave and holiday composition has no direct Attendance client and remains transitional. Attendance record and shift/policy gateway cutovers are independently controlled. The service is implemented but its ownership boundary remains Transitional during compatibility cutover.

Documentation map​

Detailed Attendance API documentation is available. Database, events, UI, operations, reference, and troubleshooting sections remain reserved for future epics.

Source References​

  • microservices/src/attendance-service/Program.cs
  • microservices/src/attendance-service/attendance-service.csproj
  • microservices/src/attendance-service/Domain/Repositories.cs
  • microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs

See Also​

Keywords​

  • Attendance Service
  • Technical architecture
  • Time Office

Revision Information​

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