The Google Cloud CDN is touted as a low cost option with tight integration with Google Cloud apps and services.
N/A
NGINX
Score 9.0 out of 10
Mid-Size Companies (51-1,000 employees)
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…
Google Cloud CDN is available globally and supports various load balancers available in different regions around the globe, so I find Google Cloud CDN as one of the best choices for CDN as it serves globally and it is really fast, safe, and secure. It might be not suitable for you if you do not have any technical background.
[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.
The intelligent categorization and management of site content cache in Google Cloud CDN is unique and offers the best results with simple settings.
It has powerful servers in all geographical regions of the world and the speed of the site will increase many times for the customer with smart routing.
It has AnyCast IP feature and website receives a single global IP address. In this case, the site loads at the same speed worldwide.
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.
I didn't have the need to use support from Google when I was either testing or setting up my website. Information was easily found by searching online if I needed to, and the options that I needed to install or enable were there on the setup page. Honestly, I was a former systems administrator so most of this stuff is not challenging for me.
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 limited software developers and don't have the need for a big cloud service provider along with their costs. Google Cloud CDN brings to usr, reliability and brand familiarity. Google Cloud CDN also doesn't bother us with pitches or 1000 emails about the products. We went and signed up for it, without dealing with a pushy salesperson.
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
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.
