I am very curious how they decided to have most infra in GCP but only DNS on AWS Route 53. I would expect that one could have everything on just GCP no?
The other interesting thing that I am starting to think more about is that every part of the infra stack will get slowly rebuilt because of AI. More load, more granular permissions, more firewalls are some of the things I can think that will need to be built in.
I like AWS DNS because it has a 100% SLA and they said they actually designed it to stop billing if needed to free up resources. You can create VERY fine grained IAM Policies that are very useful for secure automation and delegation. And of course the API is excellent.
I for one, do the same with my company. I've thought of "worse case scenarios" and the one I think among the worst is my AWS account gets hacked and ransomed. Having my DNS hosted with another provider gives me a quick way to rebuild the stack from off-site backups, switch over DNS and tell the hackers to go f$%$ themselves. If my DNS is hosted with AWS or God forbid, my registrar, then I'm just boned.
[flagged]
Most of our infra is in AWS, actually – but we do use GCP Spanner as a global control plane database, including basin metadata and its mapping from basin to cell. So for the DNS server which relies on these mappings, GCP made sense. In future we also want to run S2 cells in GCP.