Google Cloud DNS is a managed DNS service, featuring a global network of anycast servers and touting reliability, availability, and performance.
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 is well suited to access and collaborate on documents where more than 2 people are required to contribute and in instances where feedback from individuals is captured on the document itself. If a team is working on an end of year report for funders, a few key members may need to finalise a report by offering suggestions that can be viewed and resolved by other team members. Housing documents on Google Cloud is the most appropriate platform I have ever used for tasks like these. If minimal collaboration needs engagement from just 2 individuals, it may be easier to simply email the information between each other, rather than using time to create a folder, ensure access control and upload the information to Google Cloud for collaborative input
[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.
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.
This is exceptionally simple to utilize in the event that you are as of now utilizing Google Cloud Services or you are important for the Google Ecosystem as of now. I accept this is likely the primary goal of Google Cloud DNS, to give a more complete set-up of devices to Google Cloud clients. Consequently, I would rate convenience a 9.
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.
Amazon Route 53 offers almost equal or slightly more features than Google Cloud DNS; we selected Google Cloud DNS because the rest of our projects use Google Cloud Platform.
Also, since AWS is a bigger service provider, their pricing is also higher; since Google Cloud DNS pricing is better, we went for it.
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.
