Comparison between Nginx and Nginx +

Comparison between Nginx and Nginx +
I. Introduction to Nginx +

Nginx and Nginx + are both official Nginx products. The difference between the two is that Nginx is an open-source community version, while Nginx + is a paid enterprise-level version for Nginx.

Nginx + charges are as follows: for single-instance deployment, the annual fee is USD 1900. For multi-instance deployment, you need to contact the official Nginx team to negotiate the quotation.

Nginx + also provides a 30-day free trial, and you still need to pay after expiration.

Nginx + is only available in binary release, and does not provide source code.

Nginx + adds enterprise-level features based on the Nginx open-source community edition, such:

• Full-featured HTTP and TCP load balancing
• High-performance reverse proxy
• Cache and unmount Static and Dynamic Content
• Adaptive streaming media Godfather audio and video content to any device
• Application-sensitive health check and high availability
• Provides advanced activity monitoring through dashboards or APIs.
• Advanced monitoring and management: provides developer-friendly tools to manage and implement real-time changes
• Session persistence
• Consulting Service

Ii. Comparison between Nginx and Nginx +

Nginx + has some features not available in the Nginx community edition, including:

1. Advanced HTTP and TCP load balancing

In terms of the load balancing algorithm, Nginx + adds the "Least Time" (Least Time) load balancing algorithm. The "minimum time" algorithm distributes requests to server nodes with the fastest response time and the least active connections.

2. Session persistence

HTTP is a stateless protocol. Therefore, many applications are usually stored locally and cannot share the status in the Server Load balancer environment. Because the client state sharing between server nodes means that the speed is slow and implementation is troublesome. Therefore, the most common practice is to balance the load of the same terminal to the same node, you do not need to share or synchronize the status information between nodes.

Nginx + can track user sessions and distribute end users' requests to the correct upstream server node. Nginx + provides three methods to identify user sessions:

• Insert tracking information to request data

Use the sticky cookie command:

upstream backend {    server webserver1;    server webserver2;    sticky cookie srv_id expires=1h domain=.example.com path=/;}

• Detect requests in sessions

Use the sticky learn command:

upstream backend {   server webserver1;   server webserver2;   sticky learn create=$upstream_cookie_sessionid       lookup=$cookie_sessionid       zone=client_sessions:1m       timeout=1h;}

• Trace specific data in the request

Use the sticky route command:

upstream backend {   server webserver1 route=a;   server webserver2 route=b;   # $var1 and $var2 are run-time variables, calculated for each request   sticky route $var1 $var2;}

For more details, please continue to read the highlights on the next page:

For more Nginx tutorials, see the following:

Deployment of Nginx + MySQL + PHP in CentOS 6.2

Build a WEB server using Nginx

Build a Web server based on Linux6.3 + Nginx1.2 + PHP5 + MySQL5.5

Performance Tuning for Nginx in CentOS 6.3

Configure Nginx to load the ngx_pagespeed module in CentOS 6.3

Install and configure Nginx + Pcre + php-fpm in CentOS 6.4

Nginx installation and configuration instructions

Nginx log filtering using ngx_log_if does not record specific logs

1 2 Next Page

[Content navigation]
Page 1: Up	Page 1: Bottom