Amazon Route 53 vs NGINX

• We can purchase our domain through Route 53 and can be hosted for cheaper prices in AWS.
• There are many number of routing policies you can go ahead with and this will come into picture when the customer satisfaction is required at most, so choose routing policy accordingly.
• As usual health checks are part of DNS systems, this is also provided at cheaper rates when total process is done in Route 53 service.
• It can be used as standalone application from AWS

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

• Price, it is not expensive ... but you can find some cheaper and even free DNS solutions.
• If you use non-AWS infrastructure, Route 53 doesn't have significant advantages on other services.
• AWS Route 53 does not support forwarding or conditional forwarding options for domains used on an on-premise network.

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

• Route 53 has saved me a lot of time with managing DNS for clients' domains.
• Route 53 does things that normal registrar DNS can't, allowing us to better serve customers.
• Route 53 helps us avoid downtime on our websites quite regularly.

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