One of the primary things you should choose is whether it's feasible to make your web application stateless. Here's the reason.
This methodology stores your login accreditations on your PC, as opposed to the worker. Rather than checking your subtleties against the data set and concurring they're right, the worker creates an extraordinary token. Commonly, this is a long grouping of apparently irregular characters. It then, at that point sends you the token and the time allotment it'll stay legitimate.
The token is put away on a different data set, not the worker. Thus, when you choose to see your profile, you send your token close by the right URL. Also, on the grounds that the application is stateless, it doesn't make any difference where the site resides. Regardless of whether the heap balancer sends you to an alternate worker, it'll basically search for the relating token, check it against a distant information base to check whether it's substantial and utilize that as verification.