Traffic Distributor Overview

Objective

This guide explains how to use Traffic Distributor Overview 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.

One of the most common issues you can face as your project grows is the need to maintain multiple environments that may be necessary to achieve adequate capacity. (to serve all customers) such as managing different app versions You often face issues with proper traffic distribution between copies of a project including a number of different directions, such as setting the appropriate method for routing requests. server load rate, etc. Troubleshooting all of this can become challenging even for experienced developers.

Therefore, to solve these problems, Ruk-Com Cloud offers a free and easy-to-use solution based on automatic load balancer configuration, which is delivered asTraffic DistributorSpecial add-ons available For quick one-click installation via Marketplace and intelligent traffic routing based on your needs.

With this solution you can set the appropriate workload. Balance the host pair and benefit from the following features and opportunities provided:

• high availability and advanced failover- Share the load between two copies of the application. which may be indifferent hardwareTo better prevent failure
  
  
• Deploying the application Blue-Green (zero downtime)- Redirect all incoming requests to one backend while the other is under maintenance.
  
  
• A/B testing continuously- Route incoming traffic between two different versions of the application. and compare performance and UX rates to choose the best version for production.
  
  
• User-friendly UI- The configuration form allows setting all the main parameters of traffic distribution (either during creation or subsequent modification), including the availability to choose 3 different types of routes that best suit your needs: Round Robin, Sticky Sessions and Failover.
  
  
• health monitoring: Both backends are automatically checked for normal responses (e.g. return 200 status, which indicates the request has been responded to) according to configured parameters (frequency, timeout, etc.).
  
  
• Flexibility and extensibility- in addition to the main distribution settings Available via an add-on graphic interface, you can apply additional customizations you need (e.g. cache settings, TCP mapping, SNI, etc.) via manual configuration of the NGINX file - unlimited usage.
  
  

In general, compared to running a server, Traffic Distributor speeds up request processing, reduces user response delays, and handles more threads simultaneously.

How to determine the route

Distributing traffic through the Ruk-Com Cloud solution. You can choose from three routing methods to get the one that best meets your needs and suits your application, which should be considered in this section:

• Round Robin- The most straightforward and commonly used routing method that allows traffic to be evenly distributed between environments by pointing each request to them on a rotating basis (one at a time) as they are arranged according to the set backend priorities.

More:Using this option You should provide the same content as your backend (since user-requested data will be loaded from both).

• Sticky Sessions- This type of routing is based on individual user adherence. This will process all requests until the corresponding user session is established on the first app entry. It expires.

• Failover- With this type of routing you can set up a backup copy of the main server and keep it in standby mode (i.e. backup). If a problem occurs with the main backend, all requests are automatically redirected to the running server, where the user usually does not notice the application downtime.

Using TD

All you have to do to get your own Traffic Distributor is to enter a number of key parameters (e.g. select host to route requests, routing type, traffic ratio, etc.) and get started.installPressing a single button after creating the Traffic Distributor will display a separate environment with a defined number of NGINX load balancer nodes and extra add-ons installed on top.

Before installation, you can select an entry point, such that requests will be processed through a Shared Load Balancer or a public IP address.

Tips:Traffic Distributor works using the standard HTTP and HTTPS protocols and is also optimized for other similar protocols (including WebSockets). The load balancing itself is performed only during the HTTP handshake, after which a persistent WebSockets connection to the backend is established.

This way you get a very flexible Traffic Distributor that can help you achieve your goals. These range from the simple scenario of server load to more complex ones, such as using blue-green deployment to install application updates without downtime. Conducting continuous A/B testing and using advanced failover protection, among others.