Traffic Routing Management

Traffic routing management includes gateway edge traffic routing and communication traffic routing between components. The purpose of traffic routing management is to flexibly adjust the traffic direction according to business needs, and realize advanced service publishing scenarios such as gray release and A/B testing.

Gateway Edge Traffic Routing

For gateway edge traffic routing, please refer to Access to components that provide HTTP services through domain names

Communication Routing Between Components

The communication between components in Kato uses TCP Layer 4 communication by default, so there is no need to set routing parameters by default. When we want to control traffic from the application layer communication, we need to install Exit Network Management Plugin. Upgrade the communication management between services to 7-layer communication management. Currently, only Restful protocol routing management is supported, and the following routing parameters are supported:

  1. Domain name Before version 5.2.0, this domain name only supports custom top-level domain names, such as user. After version 5.2.0, it supports the definition of multi-level domain names, such as user.domian. Kato will automatically complete the domain name resolution for filling in the domain name. The Mesh layer performs routing based on the domain name accessed by the traffic.

  2. Request path Match routing strategy according to request path.

  3. Request header Perform route matching based on request header information.

In the plug-in configuration, the developer needs to perform route matching for each communication link. For example, component A depends on component B\C\D and uses domain.b domain.c domain.d domain names to communicate. Then you need to configure the domain names of the information on the links of the three components B\C\D in the plug-in configuration.