Round Robin Routing for Traffic Distributor

Objective

This guide explains how to use Round Robin Routing for Traffic Distributor on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.

Before you begin

• Sign in with an account permitted to manage the relevant environment.
• Confirm the target environment, region and resources before saving changes.
• Create a backup or rollback plan before changing a production system.

Round Robin is the most common routing method, simple and done at the same time. ForTraffic DistributorIt routes requests to backends on a rotating basis based on the specified server load, providing high availability (HA) for easily distributing applications and leveraging server load.

More:This method should only be chosen if you have identical backends content, as the user-requested data will be loaded from both servers.

Therefore, each backend is accessed according to a predefined priority level, which in the case of using Traffic Distributor is set as a percentage of all incoming requests. For example:

• If the weight is the same (e.g. 50% for both backends), every subsequent request will be directed to a different server each time. This results in equal resource use and equal traffic distribution.
  
  
• If the specified ratio is 70% to 30%, 10 consecutive requests, 7 will go to the first environment and 3 will go to the second environment, which may be useful to make this or the backend respond more or less often (e.g. to take advantage of server load).
  
  
• In case 100% is specified for any server - only the backend will be declared in the settings and will process all incoming requests, which can be used for various purposes, such as operations.Update applications invisibleor moving an environment to new hardware with no downtime.