NGINX vs. StackPath Edge Delivery

[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.

Incentivized

Well suited to:

1. Startups - Very competitive pricing, better than AWS for object storage and CDN.
2. The less technical - for those looking to implement a CDN, it doesn't get any easier than StackPath
3. The more technical - Well documented API, serverless scripting and container deployments
4. Fast object delivery - StackPath tends to be faster (sometimes much more ) than AWS S3. See below however...

Not so well suited to:

1. Multi-tiered web applications
2. Ultra high bandwidth requirements. Stackpath isn't meant to be a substitute for AWS or Azure when you're looking to push 100s of TBs of traffic.
3. Object storage works well if you don't need fine-grained bucket lifecycle or permissions management.

Incentivized

• 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)!

Incentivized

• Price competitive.
• Easy to use.
• Good reporting.
• Quick to deploy.
• Start-up friendly.
• Good technical information via blog, FAQ and community discussion.
• I can talk to real person for urgent support.

Incentivized

• 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.

• Analytics.
• Many options hidden in API.
• Web console.

Incentivized

Great value for the product

Incentivized

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.

Incentivized

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.

Incentivized

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

Incentivized

When we identified the need for having a Content Delivery Network to improve our website loading performance we researched a bit and found StackPath. Reading its reviews and the info on its website we have found that they had everything we needed so we didn't need to look for other products.

Incentivized

• 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.

Incentivized

• Easy 25-30% improvement in website performance vs non CDN solution
• Less expensive and faster object storage than AWS
• Aided greatly in maintaining KPIs in terms of performance, availability

Incentivized