Performance Technical Documentation
Summary
Complete Draft technical documentation for the source-backed Performance service architecture and implementation.
Audience
Backend and frontend engineers, architects, QA, support, security reviewers, and operators responsible for Performance.
Overview
Performance is an ASP.NET Core 8 minimal-API service with folder-based Domain/Application/Infrastructure layering, explicit repositories and unit of work, EF Core/PostgreSQL persistence, Shared Kernel observability and messaging, transactional outbox delivery, optional Workflow delegation, Gateway compatibility routing, and migration/backfill tooling.
The implementation remains Transitional because canonical and compatibility paths coexist, endpoint authorization is not enforced, and operational/testing controls remain incomplete. Pages in this section distinguish Implemented, Transitional, Foundation, Not implemented, and Requires confirmation behavior.
Documentation map
- Architecture
- Domain model
- Commands and queries
- Workflow integration
- Identity and security
- Observability
- Testing architecture
- Known limitations
Requires confirmation
Authorization policy, Gateway cutover, Workflow trust and recovery, operational ownership, service objectives, concurrency strategy, compatibility retirement, and future architecture require confirmation.
Source References
microservices/src/performance-service/performance-service.csprojmicroservices/src/performance-service/Program.csmicroservices/src/performance-service/Domainmicroservices/src/performance-service/Applicationmicroservices/src/performance-service/Infrastructuremicroservices/src/performance-service/Messagingmicroservices/src/performance-service/Backfill
Related Articles
See Also
Keywords
- Performance technical architecture
- Performance service
- Technical documentation
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly