Likelihood to Recommend - Routing users to the closest or best-performing resources: Route 53 allows you to use geolocation and latency-based routing to route users to the resources that will give them the best performance. - Load balancing: Route 53 can be used to distribute incoming traffic across multiple resources, such as Amazon Elastic Compute Cloud (EC2) instances or Amazon Elastic Container Service (ECS) tasks, to improve the availability and scalability of your application. - Managing domain names: Route 53 can be used to register domain names and manage DNS records, making it a one-stop solution for managing your domain name and routing traffic to your resources. Scenarios where Route 53 is less appropriate include:Applications with very high query rates: Route 53 is designed to handle millions of queries per second, but if your application generates an extremely high query rate, you may need to use a specialized DNS service.Applications that require very low latency: Route 53 is designed to provide low-latency DNS service, but if your application requires ultra-low latency, you may need to use a specialized DNS service or a self-hosted DNS solution.Applications that require advanced security features: Route 53 provides basic security features such as DNSSEC, but if your application requires advanced security features such as DDoS protection, you may need to use a specialized DNS service.
Read full review Azure CDN has at hand an infinity of applications and tools to implement in your system and have better control of your data in a clean and secure platform on the web, we recommend this program since the percentage of solutions provided by this program is very high and find a way to make each user's job easier.
Read full review Pros Uptime - Route53 is highly performant and available. We have had only 3-4 instances in the last 12 years when we had any downtime or outages due to Route53. Extensive API layer on Route53 that allows integration with external tools and SDK's (Boto, Terraform, etc) Closely integrated with the other AWS services. Makes it easy to operate the infra. Read full review I found the CDN very easy to setup and configure within the Azure Portal. Being Azure, there are plenty of free tools that allow you to manage the CDN from a UI that is not the portal. This was especially handy when I trained end users how to manage content within their specific realm. Read full review Cons During initial setup when you are using Route 53 or DNS systems for very first time, there are little number of documentation from AWS which is kinda of little tough. But, once you get hold of it, its a cake walk for everyone. Health checks are kinda of little costly when Compared to other big players, but that doesn't affect much when you compare its uses. The logging is well structured though its costly Read full review Tough learning curve--you have to be comfortable with the Azure Cloud logic and UI to use it easily Special or uncommon use cases' pricing can be hard to forecast/follow Can be expensive for simple use cases Read full review Usability You need to know what DNS is; this is a tool built for developers who already know the technology and are just looking for a DNS management tool. The tool is very usable given that. If you're not familiar with DNS, Route53 isn't really for you and you won't find it to be very usable-- you'll need to go read the documentation, and that will start with learning what DNS is
Read full review Support Rating Until today, I have never needed support to Route53 because the documentation is great. But, I have needed it for other services. And they're near perfect always. Except that they don't have Portuguese support yet and they're sometimes slow to answer (48 hours in non-critical ones, in two tickets). But usually, they're amazing!
Read full review Great support from the team whenever we're stuck. Very proactive in resolving issues and also making changes as per the requirements of the organization.
Read full review Alternatives Considered We purchased our domain names through Networksolutions.com and do rely on their DNS services for basic functionality (SPF hard reject records, etc.), since it was included at no cost; however, for our main domains, we utilize Route 53 because of AWS's high availability, reasonable cost, and capabilities to integrate with EC2 and other security certificate services to make hosting on AWS simple. We also front-end some of our sites with
Cloudflare and while it's not as streamlined as using AWS natively, it does a good job.
Read full review More user friendly and it’s so easy to learn, the prices may be close to each other, but the service is excellent.
Read full review Return on Investment All of our brand domain names (about 80 brands) are managed in there Many non marketing or brand domains are also in there There isn't any defined ROI because it's such a trivial and necessary service with impacts all business operations Read full review Azure CDN reduced origin instance load by removing the need to constantly serve large numbers of static files, meaning applications can be deployed with smaller/fewer instances. Azure CDN reduces apparent load times to customers by serving cached files out of POPs in the local region of those clients, instead of requiring those clients to make multiple, lengthy requests through to the origin servers. Read full review ScreenShots