Event Architecture

Summary

This page records the verified Workforce Scheduling event boundary and its adjacent Attendance integration behavior.

Audience

Developers, integration engineers, solution architects, QA engineers, and operators.

Reference Content

The only verified asynchronous path in this bounded-context neighborhood begins with Attendance aggregates. The same database save translates supported domain events into outbox rows. A hosted relay periodically publishes eligible rows. The Integration Service accepts a subset; notification and gateway components do not consume these contracts.

Ownership remains with Attendance Service for publication and the shared contracts assembly for public payload types. No saga or scheduling workflow orchestrator was found.

Source References

• microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
• microservices/src/attendance-service/Infrastructure/OutboxRelayHostedService.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
• microservices/src/integration-service/Messaging/IntegrationEventConsumer.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs
• microservices/src/gateway-api/Program.cs

Related Articles

• Events overview
• Event limitations
• Event source map

See Also

• Technical documentation
• API documentation
• Database documentation

Keywords

• Workforce Scheduling events
• Attendance integration contracts
• Transactional outbox

Revision Information

• Status: Draft
• Last reviewed: 2026-07-20
• Next review: 2026-10-20