Gateway API Boundaries
Summary
The gateway reverse proxy selects the owner of the portal-shaped Recruitment family using a feature decision. It keeps HR Operations exit traffic on the monolith and also exposes a Recruitment service shadow boundary for direct/native access.
Audience
Developers, QA, support, release engineers, security reviewers, and solution architects.
Gateway routing
Verified behavior
- Compatibility path ownership switches as a whole for the inspected Recruitment family.
- A candidate-download exception receives a more specific extracted route when selection is enabled; it is outside this lifecycle catalog.
- Generic HR Operations routing falls through to the monolith for lifecycle operations.
- The workspace path may also be claimed by other extracted domain toggles with higher-priority routes, depending on deployed selections.
- Request headers are forwarded and route source, tenant context, method, path, latency, and status are logged.
- Gateway correlation metadata is added to responses.
Security boundary
The gateway does not register or run authentication/authorization middleware in the inspected pipeline. It forwards credentials and context to targets. Route-source observability does not compensate for a missing target authorization policy.
Generated discovery
Gateway Swagger registration exists, but proxy target operations are loaded from in-memory route configuration rather than an aggregated lifecycle OpenAPI contract. Generated discovery URLs are not treated as stable module endpoints here.
Requires confirmation
- Deployed feature-selection values and route priority interactions.
- Direct/shadow exposure restrictions.
- Whether forwarded tenant context is derived, validated, or only passed through by upstream infrastructure.
- Ownership of an aggregated gateway OpenAPI definition.
Source References
microservices/src/gateway-api/Program.csmicroservices/src/shared-kernel/Middleware/CorrelationIdMiddleware.csUI/salary-ui/packages/api-client/src/axiosConfig.ts
Related Articles
See Also
Keywords
- Reverse proxy
- Route selection
- Gateway correlation
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly