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
WordPress
Score 8.6 out of 10
N/A
Wordpress is an open-source publishing platform popular with bloggers, and a content management system, known for its simplicity and modifiability. Websites may host their own blogging communities, controlling and moderating content from a single dashboard.
$3
per month 6 GB storage
Pricing
NGINX
WordPress
Editions & Modules
No answers on this topic
Personal
$4
per month 6 GB storage
Premium
$8
per month 13 GB storage
Business
$25
per month 50 GB storage
Commerce
$45
per month 50 GB storage
Enterprise
Contact for pricing
Offerings
Pricing Offerings
NGINX
WordPress
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
Pricing for Business and Commerce plans vary on number of GB.
Nnginx is more light-weight than many other web servers, has a very expressive configuration language, easier to configure than tools like IIS and Apache, easy to install certificates for SSL, much easier to model complex routing scenarios than IIS, easier to configure than …
Nginx is one of the top three web servers and sits in the second position in terms of the amount of servers deployed. The main competition comes from Apache and Apache-based forks on Linux based servers, and less-so from Microsoft IIS on Windows based servers. As stated …
Nginx has easier configuration options and speeds up the time to serve up the websites. Apache is much older and has more complicated configuration options. However, Apache's much broader config files allows for more complex situations, which may make it better in those cases. …
[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.
Wordpress is a great solution for a website of nearly any type. It may not be as suitable if a fully custom solution or app is needed, and it does have some limitations when it comes to connecting it to external products (especially if the product doesn't have any support from a native system), and it does require a lot of testing. Multiple plugins in one install are common but also increase the risk of conflicts, and when those do occur, it can be exceptionally time-consuming and tedious to identify what is causing the issue. As third parties create many plugins, you're also at risk with each potential security breach, which needs to be kept in mind. I would be cautious to use WordPress to store any sort of sensitive PPI. That said, it's a wonderful, easily customizable solution for many, many different types of websites and can allow even inexperienced client users with low-tech knowledge to update basics.
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.
WordPress breaks often so you need to have someone who understands how to troubleshoot, which can take time and money.
Some plugins are easier to customize than others, for example, some don't require any coding knowledge while others do. This can limit your project if you are not a coder.
WordPress can be easily hacked, so you also need someone who can ensure your sites are secure.
The complications we have and the lack of support. Every plugin has a differente team of support in charge and make one plugin work with the other one always affects the website performance. It's a thousand times better to have only one provider with all functionalities included unless you are an expert web developer or have a team dedicated to it
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.
Extremely easy to use and train users. It took very little time to get everyone trained and onboarded to start using WordPress. Anytime we had any issues, we were able to find an article or video to help out or we were able to contact support. The menu options are well laid out so it is easy to find what you are looking for.
Anyone can visit WordPress.org and download a fully functional copy of WordPress free of charge. Additionally, WordPress is offered to users as open-source software, which means that anyone can customize the code to create new applications and make these available to other WordPress users.
Mostly, any performance issues have to do with using too many plugins and these can sometimes slow down the overall performance of your site. It is very tempting to start adding lots of plugins to your WordPress site, however, as there are thousands of great plugins to choose from and so many of them help you do amazing things on your site. If you begin to notice performance issues with your WordPress site (e.g. pages being slow to load), there are ways to optimize the performance of your site, but this requires learning the process. WordPress users can learn how to optimize their WordPress sites by downloading the WPTrainMe WordPress training plugin (WPTrainMe.com) and going through the detailed step-by-step WordPress optimization tutorials.
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.
I give this rating, which I believe to be a great rating for a community based support system that's surrounding it. Most platforms and products have their own, and as WordPress does have their own team that help here and there, a lot of it's handled by community involvement with dedicated users who are experts with the system who love to help people.
Varies by the person providing training. High marks as it's incredibly easy to find experienced individuals in your community to provide training on any aspect of WordPress from content marketing, SEO, plugin development, theme design, etc. Less than 10 though as the training is community based and expectations for a session you find may fall short.
WordPress is not a great solution if you have: 1) A larger site with performance / availability requirements. 2) Multiple types of content you want to share - each with its own underlying data structure. 3) Multiple sites you need to manage. For very small sites where these needs are not paramount, WordPress is a decent solution
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
WordPress isn't as pretty or easy to use as certain competitors like Jimdo, Squarespace or HubSpot, but it makes up for it with its affordability, familiarity and the ability to find quality outside help easily. The same can't be said for certain competitors, as you might need to find an expert and it could get costly.
WordPress is completely scalable. You can get started immediately with a very simple "out-of-the box" WordPress installation and then add whatever functionality you need as and when you need it, and continue expanding. Often we will create various WordPress sites on the same domain to handle different aspects of our strategy (e.g. one site for the sales pages, product information and/or a marketing blog, another for delivering products securely through a private membership site, and another for running an affiliate program or other application), and then ties all of these sites together using a common theme and links on each of the site's menus. Additionally, WordPress offers a multisite function that allows organizations and institutions to manage networks of sites managed by separate individual site owners, but centrally administered by the parent organization. You can also expand WordPress into a social networking or community site, forums, etc. The same scalability applies to web design. You can start with a simple design and then scale things up to display sites with amazing visual features, including animations and video effects, sliding images and animated product image galleries, elements that appear and fade from visitor browsers, etc. The scaling possibilities of WordPress are truly endless.
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.