What users are saying about
42 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>Score 8.6 out of 100
Based on 42 reviews and ratings
93 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>Score 9.2 out of 100
Based on 93 reviews and ratings
Feature Set Ratings
Application Servers
Amazon Route 53
Feature Set Not Supported
N/A

7.9
NGINX
79%
NGINX ranks higher in 6/6 features
NGINX ranks higher in 6/6 features
IDE support
N/A
0 Ratings

8.0
80%
1 Rating
Security management
N/A
0 Ratings

8.0
80%
3 Ratings
Administration and management
N/A
0 Ratings

6.3
63%
3 Ratings
Application server performance
N/A
0 Ratings

9.0
90%
3 Ratings
Installation
N/A
0 Ratings

7.3
73%
3 Ratings
Open-source standards compliance
N/A
0 Ratings

8.5
85%
2 Ratings
Attribute Ratings
- Amazon Route 53 is rated higher in 1 area: Support Rating
- NGINX is rated higher in 1 area: Likelihood to Recommend
- Amazon Route 53 and NGINX are tied in 1 area: Usability
Likelihood to Recommend
8.3
Amazon Route 53
83%
13 Ratings

9.2
NGINX
92%
27 Ratings
Usability
9.0
Amazon Route 53
90%
6 Ratings

9.0
NGINX
90%
1 Rating
Support Rating
8.7
Amazon Route 53
87%
8 Ratings

8.1
NGINX
81%
8 Ratings
Likelihood to Recommend
Amazon Route 53
Amazon Route 53 is well suited if:
1. You seek to create a simple website fast.
2. The site would be able to host HTML5 content and static content attach a domain name.
3. Have simple and accessible management.
Scenarios where Amazon Route 53 is less appropriate:
1. If a website needs HTTPS.
2. If you need to have extensive logging and tracing on the website.
3. If a website is designed to host dynamic content.
Founder and lead developer
x2lineComputer Games, 1-10 employees
NGINX
[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.
Sr. Software Engineer
Tempus Labs, Inc.Computer Software, 1001-5000 employees
Pros
Amazon Route 53
- 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
Senior Software Engineer
BrillioInformation Technology & Services, 1001-5000 employees
NGINX
- 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)!
Senior Software Engineer
RocketripComputer Software, 11-50 employees
Cons
Amazon Route 53
- 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.

Verified User
Engineer in Other
Environmental Services Company, 11-50 employeesNGINX
- 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.
Senior DevOps Engineer
Conversant Inc. (formerly Dotomi)Marketing and Advertising, 5001-10,000 employees
Pricing Details
Amazon Route 53
General
Free Trial
—Free/Freemium Version
—Premium Consulting/Integration Services
—Entry-level set up fee?
No
Starting Price
$0.4 Per Zone Per Month
Amazon Route 53 Editions & Modules
Edition
Standard | $0.401 |
---|---|
Queries | $0.602 |
- Per Zone Per Month
- Per Million Queries
Additional Pricing Details
—NGINX
General
Free Trial
Yes
Free/Freemium Version
Yes
Premium Consulting/Integration Services
Yes
Entry-level set up fee?
Optional
Starting Price
—NGINX Editions & Modules
—
Additional Pricing Details
—Usability
Amazon Route 53
Amazon Route 53 9.0
Based on 6 answers
Like most AWS services the usability of the product is pretty good. The AWS console provides a single interface from where all the configurations can be done in a jiffy. Having said that for new users who are coming from traditional hosting services might feel a bit out of place.

Verified User
C-Level Executive in Corporate
Computer Software Company, 1-10 employeesNGINX
NGINX 9.0
Based on 1 answer
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.

Verified User
Engineer in Information Technology
Information Technology and Services Company, 10,001+ employeesSupport Rating
Amazon Route 53
Amazon Route 53 8.7
Based on 8 answers
The product is simple enough that the docs and the UI stand on their own. Its one of the least confusing (/most intuitive) AWS products. As with all Amazon products, don't expect strong email or human support-- you're going to be using their documentation. If you need a human to guide you through the DNS process, you should consider a tool like CloudFlare or NameCheap; if you're a developer, Route53 is where you want to be.

Verified User
Employee in Information Technology
Computer Software Company, 11-50 employeesNGINX
NGINX 8.1
Based on 8 answers
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. 


Principal, Lead developer, Lead designer
PelagoInternet, 1-10 employees
Alternatives Considered
Amazon Route 53
When working with AWS, Route 53 is hands down the better solution. If you live in GCP, then Google Cloud DNS is the way to go. GoDaddy is more of a consumer-facing product and is perfectly fine when Services are not being utilized in any Cloud Environment. Eventually, all of our DNS ends up in AWS or GCP...
Senior Software Engineer
CodeLinguistsComputer Software, 1-10 employees
NGINX
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
Senior Software Architect
Beneath The InkComputer Software, 1-10 employees
Return on Investment
Amazon Route 53
- 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.

Verified User
Technician in Information Technology
Information Technology & Services Company, 11-50 employeesNGINX
- 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.
Head of Development Technologies
Top Floor TechnologiesInternet, 11-50 employees