Skip to main content

Compatibility and Gateway Routing

Summary​

Gateway routing ownership for native, compatibility, shadow, and ESS traffic.

Audience​

API consumers, engineers, architects, QA, support, security reviewers, implementation partners, and product owners.

Overview​

Gateway routing decides whether the legacy HR Performance slice reaches the service. A shadow prefix can target the service without replacing legacy ownership, and ESS aggregation reads native appraisal queries.

Endpoint family​

  • The cutover switch moves only the Performance compatibility resource and workspace route.
  • Performance populates only its owned compatibility workspace section.
  • The shadow boundary removes its routing prefix before forwarding.
  • Gateway route-source logic distinguishes service, shadow, and legacy ownership.
  • Source confirms routing mechanics, not production parity or rollback approval.

Classification​

Transitional by design.

Authentication and authorization​

Bearer authentication and tenant context are registered. No Performance endpoint in this family declares an authorization requirement unless explicitly stated above.

Requires confirmation​

Cutover criteria, parity sign-off, rollback authority, public route ownership, and shadow retirement require confirmation.

Diagram​

See Also​

Keywords​

  • Performance API
  • Compatibility and Routing
  • Draft API 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