NGINX, a business unit of F5 Networks, powers over 65% of the world's busiest websites and web applications. NGINX started out as an open source web server and reverse proxy, built to be faster and more efficient than Apache. Over the years, NGINX has built a suite of infrastructure software products o tackle some of the biggest challenges in managing high-transaction applications. NGINX offers a suite of products to form the core of what organizations need to create…
N/A
Plesk
Score 9.0 out of 10
N/A
Plesk is a server control panel, providing a solution that enables usres to build and manage multiple sites from a single dashboard. Users can also run updates, monitor performance and onboard new prospects all from the same place. Plesk also boasts a robust toolkit for Wordpress management, and supports other CMS. It is available on the public cloud of the user's choice.
[NGINX] is very well suited for high performance. I have seen it used on servers with 1k current connections with no issues. Despite seeing it used in many environments I've never seen software developers use it over apache, express, IIS in local dev environments so it may be more difficult to setup. I've also seen it used to load balance again without issues.
Plesk is well-suited for website creators who have been developing websites on a regular basis. If one is new to website development, Plesk could be a bit confusing and difficult to navigate. However, if one has experience on another type of platform, like CP (Control Panel) which is used by other web hosts out there, then it will be much easier to navigate the Plesk panel. Keep in mind there is definitely a learning curve, as Plesk really is quite different. Overall, new users will learn to love the ability to have more control over their websites.
Automatically update the CMS, plugins, and templates of all your websites, depending on your CMS, all at the same time, with just a few strokes of your keyboard.
Enables one to set up a schedule to back up your websites, automatically, and easily download/save the backup files off-site, for safety.
Makes it easy for users to use a backup file to reinstall a website, with just a few strokes of the keyboard. Excellent service!
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.
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.
Community support is great, and they've also had a presence at conferences. Overall, there is no shortage of documentation and community support. We're currently using it to serve up some WordPress sites, and configuring NGINX for this purpose is well documented.
We have used Traffic, Apache, Google Cloud Load Balancing and other managed cloud-based load balancers. When it comes to scale and customization nothing beats Nginx. We selected Nginx over the others because
we have a large number of services and we can manage a single Nginx instance for all of them
we have high impact services and Nginx never breaks a sweat under load
individual services have special considerations and Nginx lets us configure each one uniquely
Plesk has a much more intuitive platform that allows for customization and scalability within an organization. It has the advantage when it comes to the ability to adapt to the current state of the company and grow with it organically. There are a few limitations that would make me choose a competitor, and there is good value for the price.
Nginx has decreased the burden of web server administration and maintenance, and we are spending less time on server issues than when we were using Apache.
Nginx has allowed more people in our company to get involved with configuring things on the web server, so there's no longer a single point of failure ("the Apache guy").
Nginx has given us the ability to handle a larger number of requests without scaling up in hardware quite so quickly.