Skip to main content

Payroll Infrastructure Layer

Summary​

Infrastructure centers on EF Core/PostgreSQL, tenant query filters, migrations, a Payroll outbox store, inbound messaging, development seeding, and in-process output adapters.

Audience​

Backend and frontend developers, QA and DevOps engineers, support and security engineers, and solution architects.

Overview​

Infrastructure centers on EF Core/PostgreSQL, tenant query filters, migrations, a Payroll outbox store, inbound messaging, development seeding, and in-process output adapters.

Technical Detail​

Persistence​

PayrollDbContext maps tenant-owned records, projections, audit/timeline evidence, processed-event markers, and outbox messages. Migrations are applied at startup unless the hosting environment suppresses that behavior.

Adapters​

The inbound event consumer is a hosted service. PDF rendering uses an in-process library and exports are composed in memory. There are no external Document Service, bank, or payment adapters in the confirmed service source.

Development and compatibility​

Development seeding exists and is guarded by the development environment. Compatibility helpers and historical backfill support transitional extraction, but operational commands and configuration details are outside this page.

Source References​

  • microservices/src/payroll-service/Infrastructure/PayrollDbContext.cs
  • microservices/src/payroll-service/Infrastructure/Persistence.cs
  • microservices/src/payroll-service/Infrastructure/DevelopmentSeeder.cs
  • microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
  • microservices/src/payroll-service/Application/PayrollPdfRenderer.cs
  • microservices/src/payroll-service/Application/PayrollOutputsService.cs

See Also​

Keywords​

  • Payroll Service
  • Payroll Infrastructure Layer
  • Technical architecture

Revision Information​

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