Likelihood to Recommend Akamai Ion is excellent if you have the staff to manage the configurations and understand how best to leverage its benefits amidst ongoing Dev work without getting in their way. You'll have to communicate consistently on what the CDN does and does not do as well as drive knowledge sharing sessions on expected behavior or unexpected behavior to help reduce unnecessary troubleshooting from your IT and Dev teams when tickets/issues arise. Akamai Ion is best suited for well equipped and well informed IT or Marketing teams that can leverage the delivery benefits of caching and offload. Doing so will increase customer satisfaction, reduce bounce rates, improve conversion rates as well as drive more time on site. Read full review [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.
Read full review Pros Ease of management with good UI for making rules and behaviors. There is also an API and Code integration for the advanced Dev-Ops team to use as well. Read full review Very low memory usage. Can handle many more connections than alternatives (like Apache HTTPD) due to low overhead. (event-based architecture). Great at serving static content. Scales very well. Easy to host multiple Nginx servers to promote high availability. Open-Source (no cost)! Read full review Cons The learning curve on using a CDN is steep and requires class time. The initial onboarding and integration with the business' DevOps teams should be a bit closer relationship. Global vs. Regional management can be a bit challenging if your account is centralized overseas, and you want a local time-zone account manager on your time. Read full review 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. Read full review Likelihood to Renew Great value for the product
Read full review Usability 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.
Read full review Support Rating Support for tickets has gotten better/quicker over the years. Also, there is a wealth of information on the knowledge base, documentation, and there is also a message board too now. Read full review John Reeve Principal, Lead developer, Lead designer
Read full review Alternatives Considered 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 Read full review Return on Investment Improved conversion rates. Reduced page load times. Read full review 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. Read full review ScreenShots