Likelihood to Recommend
Nginx is well suited for serving any static content - whether that be images, JS files, HTML files, CSS files, videos, etc. If you have a high-traffic website, Nginx will be a great fit because it handles large number of requests extremely efficiently. Nginx has full support on Unix systems, but only has limited support on Microsoft Windows machines.
I would say you can use Zend with any project of any size but in a personal experience I would recommend it more for small or medium sized projects. Since the code you will be writing with Zend has more verbosity than the one you can write with other frameworks, that might be a problem to maintain larger projects.
- Straight-forward configuration format that users of all skill levels can learn, and yet is powerful enough for the huge breadth of features that Nginx provides.
- Massive scale right out the box. We've never had a Nginx instance overwhelmed by requests, and if we did it would be trivial to spin up more Nginx instances to handle the load.
- SSL termination means that we can deliver content over HTTPS without needing our individual services to require TLS support. This saves us a lot of time and headache while keeping us secure.
- Nginx is open-source and free, meaning that anyone can use it to power their services, from individual projects to billion-dollar websites.
- The Zend Framework excels at productivity. It's lightweight, loosely-coupled enough to provide 90% of the functionality that everyone needs out of the door, but also customizeable enough to meet the remaining 10% should your business need it.
- Because the Zend Framework is functionality focused (also supported by the actual PHP developers) - it is light enough to hit the ground running with. Having no configuration files to get rolling is also a huge plus.
- The documentation of the Zend Framework is reliable, updated & succint. I have not encountered an issue that I could not easily troubleshoot from looking at the documentation.
- Customer support can be strangely condescending, perhaps it's a language issue?
- I find it a little weird how the release versions used for Nginx+ aren't the same as for open source version. It can be very confusing to determine the cross-compatibility of modules, etc., because of this.
- It seems like some (most?) modules on their own site are ancient and no longer supported, so their documentation in this area needs work.
- It's difficult to navigate between nginx.com commercial site and customer support. They need to be integrated together.
- I'd love to see more work done on nginx+ monitoring without requiring logging every request. I understand that many statistics can only be derived from logs, but plenty should work without that. Logging is not an option in many environments.
Based on 1 answer
Front end proxy and reverse proxy of Nginx is always useful. I always prefer to Nginx in overall usability when you have application server and database or multiple application servers and single database i.e. clustered application. Nginx provides really good features and flexibility which helps the system administrator in case of troubleshooting and also from the administration perspective. Also, Nginx doesn't delay any request because of internal performance issues.
Engineer in Information TechnologyInformation Technology and Services Company, 10,001+ employees
No answers yet
No answers on this topic
Based on 10 answers
I'm explicitly rating the open-source version of NGINX here. The open-source version has good documentation and useful examples. As one of the most web servers in the world, there is a wide range of tutorials and examples to learn from. This does have the drawback of potentially using older documentation, but NGINX has excellent default behavior, and the official documentation is easy to use. Their paid support seems excellent as well, though we haven't taken advantage of it yet.
Professional in Information TechnologyHuman Resources Company, 51-200 employees
No answers yet
No answers on this topic
Nginx struck the right balance for us of raw speed, power, convenience, and simplicity.
- I don't like the idea of hosting all of our open source PHP-based websites on Microsoft Windows servers with IIS, so that option was out first.
- Next, we had experience with Apache already, and were initially considering sticking with that, however it was decided that it would take too much administration time to properly configure and tune the server, especially considering it would need to occur on an ongoing basis.
- I've personally had experience with Litespeed Web Server, but we wanted something a little bit lower level--we don't need to actually manage our virtual hosts within an admin UI, and we wanted to stick with open source as much as possible. One huge benefit of Litespeed, however, is that it's .htaccess-compatible, meaning it's a much smaller transition from Apache in some cases.
- LightTPD was the closest contender to Nginx when all was said and done. We chose Nginx because some of us were more familiar with it or had some experience with it, and Nginx seemed to have more documentation and resources online for finding assistance at the time.
It isn't the fastest but is one of the faster available. It's the only one currently supported actively by the PHP team itself.You might find more classes in Symfony for instance, but in the end, most of the core files will be supported above Zend classes either by extension or by encapsulation.The only con that I see is the learning curve required to adopt this framework, and the amount of additional work you will have to do to build PHP based apps with it.
Return on Investment
- Improved the reliability of our site. Before using Nginx, with Apache as our app server, there were times when we had to manually go in and restart Apache to bring the site back online. We've never had to do that with Nginx.
- Made our web server more memory efficient -- Nginx has a very small memory footprint, on the order of under 100 MB. This makes it suitable even for cheap VPS machines.
- The Nginx community provides online examples of configurations, so it saves us time in writing the config files from scratch.
- Overall, Zend PHP Engine has had a positive return on our business objective of creating a medium sized web-application, debugging the application to assess problems before they occur, and to create dynamic API calls via our backend custom software.
Premium Consulting/Integration Services
Entry-level set up fee?
NGINX Editions & Modules
|NGINX Plus - Basic||$2,5001|
|NGINX Plus - Professional||$3,5001|
|NGINX Plus - Enterprise||$5,0001|
|NGINX WAF - Add-on||$2,0001|
- per instance
Additional Pricing Details—
Premium Consulting/Integration Services—
Entry-level set up fee?
Zend Engine Editions & Modules