On the comparison between Nginx and nginx+

Comparison of Nginx and nginx+ (UP)

Author: Chszs, not allowed to be reproduced without the permission of Bo master. Permission to reprint should be marked by the author and blog home: Http://blog.csdn.net/chszs

I. Introduction of nginx+

Nginx and nginx+ are Nginx official products, the difference is that Nginx is open-source Community edition, and nginx+ is Nginx for enterprise-class pay version.

Nginx+ charges are as follows: $1900 per year for single-instance deployments, and for multi-instance deployments, you'll need to contact Nginx official to negotiate a quote.

Nginx+ also offers a free 30-day trial, which is still subject to payment after the expiry date.

Nginx+ is provided only as a binary distribution and does not provide the source code.

Based on the Nginx Open Source Community Edition, nginx+ adds enterprise-class features such as:

• Full-featured HTTP and TCP load Balancing
• High-Performance Reverse proxy
• Caching and offloading of static content and dynamic content
• Adaptive streaming godfather audio and video content to any device
• Application-sensitive health checks and high availability
• Provides advanced activity monitoring of dashboards or API approaches
• Advanced monitoring and management, providing developer-friendly tools to manage and change in real time
• Session Persistence
• Consulting Services

Ii. comparison of Nginx and nginx+

Nginx+ has some features that are not available in the Nginx Community Edition, including:

1. Advanced HTTP and TCP load Balancing

In terms of load balancing algorithms, nginx+ adds a "Minimum Time" (Least) load balancing algorithm. The "Least time" algorithm is that the request is distributed to the server node that has the fastest response time and the least active connection.

2. Session Persistence

HTTP is a stateless protocol, so often many applications are in the state of the local storage terminal and cannot share state in a load-balanced environment. Because the sharing of state between server nodes means that the speed is slow and the implementation is cumbersome, the most common practice is to balance the same terminal load to the same node, so there is no need to share and synchronize state information between nodes.

Nginx+ can track a user's session and distribute the end user's request to the correct upstream server node. Nginx+ provides three ways to identify a user's session:

• Inserting trace information into the request data

Using the sticky cookie directive:

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

• Detecting requests in a session

Using the sticky learn directive:

upstream backend {   server webserver1;   server webserver2;   sticky learn create=$upstream_cookie_sessionid       lookup=$cookie_sessionid       z       timeout=1h;}

• Track specific data in a request

Using the Sticky route directive:

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;}

'). addclass (' pre-numbering '). Hide (); $ (this). addclass (' has-numbering '). Parent (). append ($numbering); for (i = 1; i <= lines; i++) {$numbering. Append ($ ('

'). Text (i)); }; $numbering. FadeIn (1700); }); });

The above describes the Nginx and nginx+ comparison, including the aspects of the content, I hope that the PHP tutorial interested in a friend helpful.

