Ruk-Com PaaS Documentation

Build, deploy and operate applications on the platform.

RUK-COM PAAS / APPLICATION SETTINGS

Sticky Sessions

This guide is maintained for Ruk-Com PaaS. Screens and options may vary by platform version and account permissions.

Confirm the environment, region and account permissions, and back up current settings before changing a production system.

This method is used to achieve server-affinity by sticking user to a particular backend, which allows to work with just one application version. Herewith, on the first visit, customer is routed based on the servers’ weights, while assigned backend is remembered, ensuring that all subsequent requests from this user go to the same environment.

Commonly, this is implemented through remembering IP address, which is not optimal, as there could be a lot of customers behind a proxy, resulting in unfair balancing. Thus, the platform uses an advanced solution based on the session cookies to make a persistent routing, when each browser becomes an unique “user”, allowing to make balancing more even.

Image 27: Traffic Distributor sticky sessions routing In such a way, Sticky Sessions distribution of a new users is similar to the round robin method and is performed according to the pre-set priority. For example, setting 50% to 50% will make both application versions being visited by the equal amount of unique users, which is useful for performing A/B Testing. But, irrespectively of the server’s weights, the “old” user’s requests will always be redirected to the hosts they are assigned to, until their session is expired or cookie is removed.