Performance and Scaling

Summary

Current query bounds, asynchronous delivery, and confirmed scaling gaps.

Audience

Engineers, architects, QA, support, security reviewers, and operators working with the Performance module.

Overview

List and compatibility reads apply fixed upper bounds, reports use direct EF Core projections, and event publication is moved out of the request transaction through the outbox relay.

Confirmed implementation

• Tenant and common lifecycle lookups have persistence indexes in source mappings.
• Appraisal command loads include owned child collections.
• Reports execute against primary persistence without cache or a separate analytical store.
• Outbox delivery processes bounded batches in a background loop.
• No distributed cache, explicit concurrency marker, rate limiting, bulkhead policy, or service-specific performance instrumentation is implemented.

Classification

Foundation scaling posture.

Requires confirmation

Workload targets, pagination, cache policy, concurrency behavior, report isolation, rate limits, and capacity testing require confirmation.

Related Articles

• Performance technical documentation
• Performance module

See Also

• Technical known limitations
• Performance business documentation

Keywords

• Performance service
• Performance and Scaling
• Draft technical documentation

Source References

• microservices/src/performance-service/Application/Queries/PerformanceQueries.cs
• microservices/src/performance-service/Application/Queries/PerformanceReports.cs
• microservices/src/performance-service/Infrastructure/Persistence.cs
• microservices/src/performance-service/Messaging/OutboxRelayHostedService.cs

Revision Information

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