Performance Application Layer

Summary

Application orchestration, ports, results, and transaction boundaries.

Audience

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

Overview

The Application folder uses explicit service classes for writes and reads. It does not use a mediator library. Commands orchestrate domain methods, auditing, timelines, integrations, and a unit-of-work save; queries compose tenant-filtered repository queryables.

Confirmed implementation

• A lightweight generic Result type represents success and known error categories.
• Commands catch domain validation failures and return invalid results.
• Queries project entities into DTOs through explicit mapping extensions.
• Audit and timeline ports are invoked in the same save boundary as canonical mutations.
• Workflow start can introduce a second save after self submission.

Classification

Implemented custom CQRS-style organization without pipeline behaviors.

Requires confirmation

Cross-cutting command pipeline, standardized retry policy, and transaction strategy across remote calls require confirmation.

Related Articles

• Performance technical documentation
• Performance module

See Also

• Technical known limitations
• Performance business documentation

Keywords

• Performance service
• Application Layer
• Draft technical documentation

Source References

• microservices/src/performance-service/Application/Common/Cqrs.cs
• microservices/src/performance-service/Application/Common/Abstractions.cs
• microservices/src/performance-service/Application/Commands
• microservices/src/performance-service/Application/Queries

Revision Information

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