I'm Taryn's coworker I was involved in that part of the process very closely. That statement is not entirely accurate. The SSDs certainly did die, but not _because_ of the 2019 upgrade, it just happened at the same time…
Not sure if trolling or... but fwiw at Stack Overflow's SRE team we use Go a _lot_. We just open-sourced our latest tool written in Go, DNSControl (https://github.com/StackExchange/dnscontrol/), and we have dozens of…
That was my takeaway too. If you ever had to change a spelling error in the front-end of a devopsy-style tool, then chances are you wrote some javascript, and bam: top of the list.
I'm in the camp of "I do all my serious work on a PC, but I take a MacBook to conferences because it's light and has good battery life".
So DNSMadeEasy made it all the way through the barrage of tests. I even wrote a library for their API so that we could integrate it into our DNS software (https://github.com/mhenderson-so/godnsmadeeasy), but at the end…
Author here. CloudFlare's DNS was measurably, and consistently, faster than almost every provider we tested. So I can concur with you in that regards. It was ultimately faster than Route 53 and Google Cloud (the path we…
Author here. I agree. There are built-in mechanisms for doing this - AXFR and IXFR. However, these mechanisms were not really designed with this sort of scale in mind. You have to keep an up to date whitelist of all the…
Author here. Google and AWS are anycasted services. We were not interested in running our own anycasted DNS due to the management overhead of doing so, and because the cost of anycasting our own services would be orders…
Author here. One thing I didn't cover in the post was about how to have Google and AWS honour their SLA's is that you have to use _all 4_ of the nameservers they provide. Because we're not doing that (only using half),…
I'm Taryn's coworker I was involved in that part of the process very closely. That statement is not entirely accurate. The SSDs certainly did die, but not _because_ of the 2019 upgrade, it just happened at the same time…
Not sure if trolling or... but fwiw at Stack Overflow's SRE team we use Go a _lot_. We just open-sourced our latest tool written in Go, DNSControl (https://github.com/StackExchange/dnscontrol/), and we have dozens of…
That was my takeaway too. If you ever had to change a spelling error in the front-end of a devopsy-style tool, then chances are you wrote some javascript, and bam: top of the list.
I'm in the camp of "I do all my serious work on a PC, but I take a MacBook to conferences because it's light and has good battery life".
So DNSMadeEasy made it all the way through the barrage of tests. I even wrote a library for their API so that we could integrate it into our DNS software (https://github.com/mhenderson-so/godnsmadeeasy), but at the end…
Author here. CloudFlare's DNS was measurably, and consistently, faster than almost every provider we tested. So I can concur with you in that regards. It was ultimately faster than Route 53 and Google Cloud (the path we…
Author here. I agree. There are built-in mechanisms for doing this - AXFR and IXFR. However, these mechanisms were not really designed with this sort of scale in mind. You have to keep an up to date whitelist of all the…
Author here. Google and AWS are anycasted services. We were not interested in running our own anycasted DNS due to the management overhead of doing so, and because the cost of anycasting our own services would be orders…
Author here. One thing I didn't cover in the post was about how to have Google and AWS honour their SLA's is that you have to use _all 4_ of the nameservers they provide. Because we're not doing that (only using half),…