Skip to main content

Performance Operational Checklist

Summary​

Audience​

Operations, support, engineering, QA, security, and change reviewers.

Reference Content​

Before an approved change​

  • Confirm scope, owners, backup/recovery responsibility, compatibility mode, dependency readiness, migration review, and synthetic validation data.
  • Confirm Workflow selection, messaging/Notification expectations, and unresolved parity gaps without recording values.

After startup or change​

  • Confirm supported health, canonical reads, tenant isolation, expected lifecycle mutation, audit/timeline evidence, outbox state progression, and dependency-specific evidence.
  • Run approved non-production smoke/parity coverage proportional to change risk.

Stop and escalate​

Stop for unexplained tenant crossover, migration mismatch, repeated Workflow/publication failure, unexpected compatibility divergence, missing audit evidence, or unclear recovery authority.

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/Api/PerformanceEndpoints.cs
  • microservices/src/performance-service/Messaging/OutboxRelayHostedService.cs

See Also​

Keywords​

  • Performance operations
  • Safe support guidance

Revision Information​

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