Skip to main content

Employee Integration Points

Summary

Employee Service integrates through Gateway routing, authenticated Identity context, shared contracts/outbox records, and confirmed downstream consumers. It has no direct compile-time reference to another domain service and no registered external HTTP client.

Audience

  • Backend developers and QA engineers
  • DevOps engineers, solution architects, and security engineers

Overview

Integration graph

Confirmed relationships

BoundaryInteraction
GatewaySelects Employee or monolith ownership during cutover and contains Employee shadow/direct routing support.
IdentitySupplies accepted authenticated user/tenant context through bearer tokens; no direct service call was found.
PlatformOwns tenant/company control plane and records receipt of selected Employee lifecycle messages; no Employee-to-Platform HTTP client was found.
OrganizationDepartment and designation behavior is implemented inside Employee Service.
LeaveConsumes selected Employee lifecycle messages into a local employee profile.
PayrollConsumes selected Employee lifecycle messages into a local payroll workforce read model.
NotificationResolves employee-creation activity into notifications.
AttendanceHolds employee profile data, but automatic Employee message consumption was not found.

The Employee outbox creates integration records, but the Employee host does not register a relay worker. End-to-end publication from this service Requires confirmation.

Source References

  • microservices/src/employee-service/Program.cs
  • microservices/src/employee-service/Infrastructure/EmployeeDbContext.cs
  • microservices/src/gateway-api/Program.cs
  • microservices/src/platform-service/Messaging/PlatformEventConsumer.cs
  • microservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs
  • microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
  • microservices/src/notification-service/Application/EventNotificationResolver.cs

See Also

Keywords

  • Runtime integration
  • Downstream consumer
  • Service boundary

Revision Information

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