Internal Routing
Inputs to routing
After validation, the gateway routes the request to exactly one domain owner. Routing is deterministic and version-aware.
Endpoint path and API version.
Request intent (resource, verb, and query shape).
Feature flags for safe rollouts, when used.
Routing properties
Deterministic. Same inputs route to the same service.
Version-aware. Existing integrations keep working as newer APIs ship.
Thin gateway. Domain transformations happen in the domain service.
This prevents internal services from becoming input-validation layers.
Sanitizes and validates parameters.
Enforces required fields and allowed ranges.
Drops unknown fields when strict validation applies.
Before forwarding, the gateway:
Parameter forwarding rules
Last updated