The NGINX balancer stack is HTTP/3 ready with the feature support enabled by default since the 1.16.1 release. Herewith, a public IP address is required to bypass the Shared Load Balancer and work directly with the server over HTTP/3.
NGINX is an open-source TCP/UDP, HTTP, and reverse proxy server. It is one of the most popular solutions for load balancing in the world, which provides customers with high performance and efficient resource usage. The modular architecture of NGINX ensures personalized customization that can support all of the customers’ needs, including such features as:
Load balancing with NGINX is suitable for most of the cases due to its scalability, security, reliability, and cost-efficiency. Creating a new NGINX-based load balancer is a straightforward process at CirrusGrid PaaS.
1. Log in to the dashboard and click the New Environment button at the top-left corner.
2. Within the automatically opened topology wizard, select NGINX at the Balancing section (circled in the image below). Herewith, if a load balancer is added to the environment with the application server(s), all the required configurations to distribute requests among available instances will be applied automatically.
Next, you need to set the desired configurations for your NGINX balancer (cloudlets, disk space, IP addresses, etc.), add any other needed stacks (e.g. application servers or databases), and click Create.
3. Wait a moment for the platform to set up the environment for you.
Congrats, your NGINX load balancer is ready to work! Now, you can proceed to its configuration.
Powered by BetterDocs
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.