Skip to main content

Performance Rollback Boundaries

Summary​

No complete automated Performance rollback runbook is confirmed. Source supports compatibility coexistence, backfill modes, parity checks, and cutover assessment, but not an authorization to reverse production state.

Rollback planning must distinguish routing/configuration rollback, application release rollback, schema compatibility, data written after cutover, outbox state, Workflow instances, and Notification effects. Some external effects cannot be transactionally undone.

Classification: Foundation. Stop at evidence collection and escalate to approved change, database, integration, and product owners.

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/scripts/performance-cutover-go-no-go.ps1
  • microservices/src/performance-service/Backfill/PerformanceBackfillTypes.cs
  • microservices/src/performance-service/Application/Compatibility/PerformanceCompatService.cs

See Also​

Keywords​

  • Performance operations
  • Safe support guidance

Revision Information​

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