Asset Compatibility UI
Summary
The asset UI communicates exclusively with monolith-shaped compatibility endpoints. A gateway asset-routing feature flag can transitionally route the asset slice to the asset service, with a shadow route and a route-source response header. The frontend is unchanged by this cutover. The classification is Transitional.
Audience
- Developers reasoning about the compatibility layer.
- QA engineers validating both routing sides.
- Support engineers explaining cutover behaviour.
- Solution architects reviewing the transitional architecture.
Reference Content
Compatibility endpoints used by the UI
The UI talks to monolith-shaped compatibility endpoints:
- The HR Operations workspace (asset list load).
- Asset request creation (
/hr-operations/asset-requests). - Asset status change (
/hr-operations/assets/{id}/status). - Asset delete.
Gateway asset-routing flag
When the asset-routing feature flag is ON at the gateway, only the asset slice routes to the asset service: the asset endpoints (/api/hr-operations/assets/**), asset requests (/api/hr-operations/asset-requests), and the workspace slice. When the flag is OFF, the monolith serves these requests.
Shadow routing and route-source header
A shadow route exists alongside the primary route, and an X-Gateway-Route-Source response header indicates which source served the request. These support safe, observable cutover.
Transitional cutover, frontend unchanged
This is a transitional cutover between monolith and asset service. The frontend is not modified by the cutover — it continues to call the same compatibility endpoints regardless of which backend serves them. The UI has no awareness of the routing decision beyond the response it receives.
Classification
The compatibility UI is classified as Transitional.
Source References
microservices/src/gateway-api/Program.csmicroservices/src/asset-service/Api/AssetCompatEndpoints.csUI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx
Related Articles
See Also
Keywords
compatibility endpoints, asset-routing flag, shadow routing, route source header, transitional cutover
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly