Sometimes I write code.

Load balancing your web application is the way to go when expecting or experiencing a large amount of traffic, but when it comes to designing an authentication and authorization flow it can become more complicated on the back-end side.

Why load balance?

In high traffic scenarios, such as hosting a social networking website, a popular blog, an API or just about any app on the Internet with a large number of valid incoming requests it can be overwhelming for the physical server to handle all of these requests and produce the desired responses.

Continuing I will be discussing the apparent and deeper implications of scaling up your authentication and authorization flow (auth from now on) handled by your web server into a system which cannot guarantee that subsequent requests from the same client will be handled by the same server. …

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store