Performance Operations Documentation

Summary

Performance Service owns canonical persistence, compatibility APIs, audit/timeline evidence, Workflow delegation, and outbound outbox intent.

Audience

Support, operations, engineering, QA, architecture, security, and implementation teams.

Overview

Runtime dependencies are database persistence, tenant/authentication context, gateway routing, optional Workflow HTTP integration, messaging publication, and downstream Notification consumption. Source-backed pages define observable boundaries without becoming production runbooks.

Documentation map

• Runtime, configuration, startup, and health
• Workflow, Notification, and outbox
• Compatibility/cutover, smoke testing, and rollback
• Escalation and operational checklist

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

Related Articles

• Performance operations
• Performance troubleshooting

See Also

• Technical documentation
• Events documentation

Keywords

• Performance operations
• Safe support guidance

Revision Information

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