Skip to main content

Performance Startup and Readiness

Summary​

Startup builds the web host, registers shared observability/messaging, persistence, handlers, optional Workflow integration, authentication/authorization services, health checks, and the outbox hosted service. Development can apply migrations and seed data; production migration ownership is not defined here.

Safe readiness evidence is successful process initialization, successful supported health response, persistence availability, and absence of repeated dependency/relay warnings in approved telemetry. Do not infer business readiness from process health alone.

Deployment sequencing, migration approval, startup timeout, readiness gating, and production seeding policy require confirmation.

Safety and confirmation boundary​

No production command, secret, configuration value, internal address, infrastructure detail, direct data change, or replay instruction is provided. Production ownership, approvals, service objectives, alerting, and recovery authority require confirmation.

Source References​

  • microservices/src/performance-service/Program.cs
  • microservices/src/performance-service/Infrastructure/DevelopmentSeeder.cs
  • microservices/src/performance-service/Infrastructure/PerformanceDbContext.cs

See Also​

Keywords​

  • Performance operations
  • Safe support guidance

Revision Information​

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