📄️ Nginx Balancer
The NGINX balancer stack is HTTP/3 ready with the feature support enabled by default since the 1.16.1 release. However, a public IP address is required to bypass the Shared Load Balancer and work directly with the server over HTTP/3.
📄️ TCP Load Balancing
Load balancing ensures high system availability through the distribution of workload across multiple components. Using multiple components with load balancing, instead of a single component, may increase reliability through redundancy. The platform uses NGINX for two types of load balancing: TCP and HTTP.
📄️ Nginx Balancer Configuration
The following NGINX configuration files are available:
📄️ Testing Load Balancing
When your project becomes highly demanded and visited, you face a problem - necessity to increase your hardware productivity, as it should be able to handle and rapidly serve all the incoming users' requests. Adding more resources will temporarily improve the situation, saving your server from the failure, but won’t solve the root issue. And this results in the need to set up a clustering solution with an embedded automatic load balancing.
📄️ Caching In Nginx Balancer
Caching in NGINX is the process of storing data in front of web servers. For example, the files a user automatically requests by looking at a web-page can be stored in your NGINX cache directory. When a user returns to a page he’s recently looked at, the browser can get those files from the NGINX cache directory rather than the original server, saving time and traffic.
📄️ App Security With Nginx Balancer
Basic Security for Applications with NGINX Balancer
📄️ Nginx Modsecurity
ModSecurity is an open-source, cross-platform web application firewall (WAF) module that helps to detect and prevent various attacks against web applications. The module can block common code injection attacks that ensures higher level of server security. It comes with a set of rules for cross website scripting, SQL injection, bad user agents, session hijacking, trojans, and other exploits.