Gateway Integration

Summary

Gateway ownership of native, compatibility, shadow, and ESS Performance routing.

Audience

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

Overview

The Gateway owns client-facing transition routing. A routing decision controls whether the legacy HR Performance slice is handled by the service, while a separate shadow boundary and native service access remain available. ESS aggregation also reads Performance.

Confirmed implementation

• Only the Performance slice of the legacy HR workspace is moved by the compatibility switch.
• Gateway route selection is observable through its routing source logic.
• ESS uses subject-scoped Performance reads.
• The service provides a legacy-shaped compatibility endpoint module.
• Business documentation URLs are independent of runtime route changes.

Classification

Transitional while legacy and service-native routing coexist.

Requires confirmation

Cutover criteria, rollback authority, public route ownership, and eventual shadow removal require confirmation.

Diagram

Related Articles

• Performance technical documentation
• Performance module

See Also

• Technical known limitations
• Performance business documentation

Keywords

• Performance service
• Gateway Integration
• Draft technical documentation

Source References

• microservices/src/gateway-api/Program.cs
• microservices/src/gateway-api/EssEndpoints.cs
• microservices/src/performance-service/Api/PerformanceCompatEndpoints.cs

Revision Information

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