Google Cloud DNS: This is Google Cloud's offering, designed to provide high-performance and premium networking. - Source: dev.to / 9 months ago

Google's enterprise-grade DNS is "Google Cloud DNS" [1]. It's not going anywhere. Google Domains is a consumer-grade product, in the sense that it is lacking most of the features (access control, bulk management) that a large company needs, though it was not lacking in stability / availability. And you could easily hook Google Domains up to Google Workspace to light up email for a small business. Feels like a good... - Source: Hacker News / almost 1 year ago

Why not use Cloud DNS and Cloud Storage to host a static website? Source: over 1 year ago

Another solution similar to DNS stubs is to use a managed DNS product. In the case of GCP there is the Cloud DNS product, which handles replicating local DNS entries up to the VPC level for resolution by outside clusters, or even virtual machines within the same VPC. This option offers a lot of benefits, including:. - Source: dev.to / over 2 years ago

You are 100% right that the domain is the keys to the kingdom. Definitely only use registrars and DNS providers that have 2FA. Google has a registrar now, as well as DNS in GCP https://cloud.google.com/domains/docs/register-domain and https://cloud.google.com/dns. By using those you can leverage your Google account's security (use separate accounts for admin level access on GCP and enforce hardware 2FA), and... - Source: Hacker News / over 2 years ago

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

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: about 2 years ago

Apache Traffic Server (no relation to Apache itself) would be an excellent option: https://trafficserver.apache.org/. - Source: Hacker News / over 2 years ago

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

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