Skip to main content
Version: 1.2

Load Balancer


architecture diagram

Table of Contents​

NGINX​

For the load balancer, we chose to use a simple NGINX configuration, that allows us to tune how the distribution of work is made between the API instances (round-robin, response time, etc) and does not introduce a large processing overhead into our system.

Since the system is user-based, the backend must provide the responses in a timely manner, so any overhead introduced must be reduced to a minimum.

NGINX also allows us to automatically intercept and filter large files as soon as the requests carrying them are received in the backend, preventing these files from taking up too much processing power to analyze.

So with NGINX we can:

  • Balance the processing load more efficiently across our API Instances;
  • Prevent large files from having to be processed, discarding them as soon as possible;
  • Reduce the overhead introduced into the system by other large load balancers.