How Did Four Unicast Servers on Linode and a Small Orange Push Anthony Eden to Treat Domain Name System Scale as a Long-haul Job of Continuous Evolution?
Anthony Eden says a domain name system business only runs at any sort of scale when the operator stays willing to continue evolving over time. The first infrastructure could not scale at all, and it did not look anything like the system in place later.
The first rollout was four Unicast servers running on VPSs. The servers sat at Linode and at a small orange, really tiny companies doing VPSs, and the setup was terrible. Because the design was Unicast, if one server went down everybody was impacted. It was a hot mess, but the team had to start somewhere.
Eden says any infrastructure company has to be ready for the long haul and willing to continuously evolve. The standard, ideally, is that customers cannot be impacted by the changes, and the operator wants to keep evolving without bringing the service down as a whole. The lesson only lands after operating the service for a while.
People
On this episode
- How Did Anthony Eden Pass a Seven-day Domain Registrar Test in 1999 and Become One of the First Seven Sellers of Dot Com Names? Transcript
- How Did Replicating Postgres Zone Data to Each Edge Cut an Australia Name Server Reload From Almost an Hour to Four Minutes? Transcript
- How Did Four Unicast Servers on Linode and a Small Orange Push Anthony Eden to Treat Domain Name System Scale as a Long-haul Job of Continuous Evolution? Transcript
- How Did Anthony Eden Institutionalize a Blameless Post-incident Review So Every Incident Gets a Record of What Happened and a Commitment to Take Action? Transcript
- How Did a Few Months Building a Knowledge Base Pull Dnsimple Back to Staying Focused? Transcript
- Why Does Leaving Space Open Give Anthony Eden Optionality to Follow a New Idea at Work or at Home? Transcript