Software Alternatives, Accelerators & Startups

Amazon Route 53 VS Apache Traffic Server

Compare Amazon Route 53 VS Apache Traffic Server and see what are their differences

Amazon Route 53 logo Amazon Route 53

Amazon Route 53 is a highly available and scalable DNS web service.

Apache Traffic Server logo Apache Traffic Server

Fast, scalable and extensible HTTP/S 2 and 1.1 compliant caching proxy server.
  • Amazon Route 53 Landing page
    Landing page //
    2022-01-28
  • Apache Traffic Server Landing page
    Landing page //
    2018-09-29

Amazon Route 53 videos

AWS re:Invent 2018: Introduction to Amazon Route 53 Resolver for Hybrid Cloud (NET215)

Apache Traffic Server videos

Transparent HTTP proxying with Apache Traffic Server

More videos:

  • Review - Yahoo's Adventure with Apache Traffic Server - Shu Kit Chan, Vijay Prashanth Hosahithlu

Category Popularity

0-100% (relative to Amazon Route 53 and Apache Traffic Server)
Cloud Computing
100 100%
0% 0
Proxy Server
0 0%
100% 100
Domain Name Registrar
100 100%
0% 0
Proxy
0 0%
100% 100

User comments

Share your experience with using Amazon Route 53 and Apache Traffic Server. For example, how are they different and which one is better?
Log in or Post with

Social recommendations and mentions

Based on our record, Amazon Route 53 should be more popular than Apache Traffic Server. It has been mentiond 45 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

Amazon Route 53 mentions (45)

  • I used Cloudflare Workers and R2 as HTML generating service. It was so easy!
    Also, I moved my domain (cora-pic.com) from Amazon Route 53 to Cloudflare Registrar to use custom domain for Worker and R2. - Source: dev.to / about 2 months ago
  • How I - well, AWS WAF and CloudFront - saved the day for my client
    We moved my clients main DNS zone to the Route53 service (luckily, all the preparatory census work had been carried out before). This brings at least two benefits:. - Source: dev.to / 3 months ago
  • Amazon Route 53 Routing Policies: A cornerstone component in improving performance & availability
    Amazon Route 53 is a highly available and scalable Domain Name System (DNS) service that allows users to route end-users to internet applications. AWS Route53 is a versatile service that can be used to manage domain registration, create and manage DNS records, and configure health checks to monitor the health and performance of resources. In this article, we’ll take a closer look at the different routing policies... - Source: dev.to / 8 months ago
  • Authenticating users in the load balancer with Cognito
    In this case, we configure MY_CUSTOM_DOMAIN to be an alias A record in Route 53 with the load balancer being the target value. - Source: dev.to / 9 months ago
  • Understanding Amazon Route 53: An In-depth Guide
    In today's cloud-centric world, one of the most crucial services often overlooked is the Domain Name System (DNS). A robust DNS service is foundational to ensure that your web applications are scalable, secure, and highly available. One such leading service in this space is Amazon Route 53, part of Amazon Web Services (AWS). This blog post aims to provide a comprehensive guide on what Amazon Route 53 is, its... - Source: dev.to / 9 months ago
View more

Apache Traffic Server mentions (5)

  • Wikipedia now has up to 1000X reduction of ATS disk read latency at the p999
    Apache Traffic Server: https://trafficserver.apache.org/ Here’s how they use it along with Varnish: https://wikitech.wikimedia.org/wiki/Caching_overview. - Source: Hacker News / over 1 year ago
  • How does Content delivery/distribution network work?
    The LARGE majority of CDNs use either Apache Traffic Server (https://trafficserver.apache.org/) or Nginx for their cache webserver, so the mechanisms used are pretty easy to find if you look through the docs. Source: almost 2 years ago
  • Using Nginx as an Object Storage Gateway
    Apache Traffic Server (no relation to Apache itself) would be an excellent option: https://trafficserver.apache.org/. - Source: Hacker News / over 2 years ago
  • Build a CDN in about 5 hours
    We have choices. We could use Varnish (scripting! Edge side includes! PHK blog posts!). We could use Apache Traffic Server (being the only new team this year to use ATS!). Or we could use NGINX (we're already running it!). The only certainty is that you'll come to hate whichever one you pick. Try them all and pick the one you hate the least. - Source: dev.to / almost 3 years ago
  • Isp.netscape.com
    I was curious if I could find anything out about their stack. Turns out they are using something called Apache Traffic Server[0]. > Formerly a commercial product, Yahoo! Donated it to the Apache Foundation [0] http://trafficserver.apache.org/. - Source: Hacker News / about 3 years ago

What are some alternatives?

When comparing Amazon Route 53 and Apache Traffic Server, you can also consider the following products

Cloudflare DNS - Install the free app that makes your phone’s Internet more fast, private, and reliable.

Squid Proxy - Website Content Acceleration and Distribution. Thousands of web-sites around the Internet use Squid to drastically increase their content delivery. Squid can reduce your server load and improve delivery speeds to clients.

ClouDNS - ClouDNS is a platform that allows users to keep their websites, data, and network security all the time.

3proxy - 3proxy freeware proxy server for Windows and Unix. HTTP, SOCKS, FTP, POP3

Google Cloud DNS - Reliable, resilient, low-latency DNS serving from Google’s worldwide network of Anycast DNS servers.

CCProxy - Want to share Internet connection? Get every computer online through a single Internet connection?