Skip to main content

Payroll Configuration and Startup

Summary​

This page records confirmed payroll configuration and startup behavior and marks incomplete boundaries explicitly.

Audience​

Payroll users, developers, QA and support engineers, architects, and implementation reviewers.

Configuration categories​

Confirmed categories are service identity/observability, persistence connectivity, messaging connectivity, tenant/request context, migration suppression, and environment-specific development seeding. Names and values are intentionally excluded.

Startup sequence​

The process selects backfill mode before web-host startup when requested. Normal startup builds services, applies migrations unless suppressed, attempts development seeding only in development, configures middleware, and maps health/service/API routes.

Failure behavior​

Migration failure is not caught in Program and can prevent startup. Development seeding failure is logged and startup continues. The projection worker retries broker connection without crashing host startup.

Hosted services​

PayrollReadModelConsumer is the only Payroll-hosted worker confirmed. A hosted outbox relay is not registered.

Requires confirmation​

Production configuration ownership, secret delivery, migration suppression approval, and startup dependency policy.

Source References​

  • microservices/src/payroll-service/Program.cs
  • microservices/src/payroll-service/Infrastructure/PayrollDbContext.cs
  • microservices/src/payroll-service/Infrastructure/Persistence.cs
  • microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs

See Also​

Keywords​

  • Payroll operations
  • Payroll Configuration and Startup

Revision Information​

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