Skip to main content

Employee Technical Limitations

Summary​

Employee Service is implemented but remains transitional. Confirmed gaps affect routing ownership, CQRS consistency, authorization coverage, message publication, health depth, observability, integration completeness, and automated verification.

Audience​

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

Reference Content​

Confirmed limitations​

  1. Outbox relay: the service stores pending outbox records and registers an on-demand processor, but no hosted relay invokes it.
  2. CQRS duplication: typed command/query handlers coexist with EmployeeCommands and EmployeeQueries application services.
  3. Pipeline behaviors: the Behaviors folder contains future guidance only; validation, audit, transaction, idempotency, and telemetry are not centralized in a pipeline.
  4. Authorization attachment: permission names and authenticated-user policies exist, but consistent fine-grained enforcement across presentation mappings was not confirmed.
  5. Gateway cutover: Employee and monolith compatibility ownership coexist behind Gateway routing configuration and shadow support.
  6. Attendance synchronization: Attendance has local employee profiles but no confirmed Employee lifecycle consumer.
  7. Integration delivery: Leave, Payroll, Platform, and Notification consumers exist, but Employee publication in every environment is unproven because of the relay gap.
  8. Health depth: only a general health endpoint is registered; persistence, broker, outbox, readiness, and liveness checks are absent.
  9. Metrics: no Employee metrics pipeline or custom metrics were found.
  10. Caching: no Employee cache is registered.
  11. External storage: Employee stores document references but has no binary-storage adapter.
  12. Validation parity: cross-entity validation differs between the two application styles and is not uniformly pipeline-enforced.
  13. Source-adjacent guidance: several Application README files describe future handlers even though handler implementations now exist, so those notes are stale.
  14. Automated tests: the backend inventory found no .NET test project; validation relies on smoke/parity tooling and source review.

Migration status​

Employee has direct, foundation, and compatibility presentation mappings. Gateway-controlled ownership and monolith coexistence demonstrate an active migration rather than a completed cutover. Production route selection and retirement milestones Require confirmation.

These limitations are stated at architecture level and do not disclose secrets, exploit instructions, environment values, schema details, or event payloads.

Source References​

  • microservices/src/employee-service/Program.cs
  • microservices/src/employee-service/Application/Behaviors/README.md
  • microservices/src/employee-service/Application/Employees/Employees.cs
  • microservices/src/employee-service/Application/Commands/EmployeeApplicationCommands.cs
  • microservices/src/employee-service/Infrastructure/Persistence.cs
  • microservices/src/gateway-api/Program.cs
  • documentation-inventory/hr-suit-backend-source-inventory.md

See Also​

Keywords​

  • Transitional architecture
  • Missing worker
  • Migration limitation

Revision Information​

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