Skip to main content

Gateway and Request Routing

Summary​

The HR Suit gateway uses YARP and custom aggregation endpoints to route stable client requests to either the active monolith or extracted services during incremental modernization.

Audience​

  • Developers and QA engineers
  • DevOps engineers
  • Implementation partners
  • Solution architects

Overview​

Gateway routes and downstream clusters are assembled in memory from application configuration. This supports configuration-controlled selection between monolith and service targets without publishing the internal route table.

The gateway forwards authorization context to downstream applications. Authentication and authorization are primarily enforced downstream, where the target application applies its own policies. Tenant and correlation context are carried through request processing for tenant-aware behavior and traceability.

For employee self-service (ESS) aggregation, the gateway combines selected downstream results. It can return a partial result when one dependency is degraded, allowing callers to distinguish a usable partial response from a complete response.

Transitional behavior​

  • Monolith-versus-service routing: eligible routes select a target using configuration.
  • Authorization forwarding: incoming authorization context is forwarded; downstream policies remain authoritative.
  • Tenant and correlation context: request context supports tenant-aware processing and cross-component tracing.
  • Compatibility and shadow paths: transitional paths can preserve contracts or support comparison during extraction.
  • Rollback: routing configuration can return traffic to the monolith if a cutover does not meet acceptance criteria.

This public page intentionally excludes exact routes, configuration keys, host addresses, and environment values.

See Also​

Keywords​

  • Reverse proxy
  • Downstream authorization
  • Aggregated response

Revision Information​

  • Last reviewed: 2026-07-14
  • Owner: architecture-team
  • Status: Draft