3 ms·
If you are interested in "latency-based" DNS routing, I'm giving a talk at Velocity in June about how we do it at Facebook: http://velocityconf.com/velocity201
by aristus 14y ago
If you are interested in "latency-based" DNS routing, I'm giving a talk at Velocity in June about how we do it at Facebook:
http://velocityconf.com/velocity2012/public/schedule/detail/23732 http://velocityconf.com/velocity2012/public/schedule/detail/...
Slides: http://www.slideshare.net/aristus/doppler-12564220 http://www.slideshare.net/aristus/doppler-12564220
- cperciva 14y agoFor what it's worth, I decided to use Route 53 for this precisely because of the hard issues you discuss in your talk: Amazon has a huge amount of data at their disposal to use in figuring out how to route traffic. This is one of the areas where the scale of AWS gives them an unfair advantage, and for $2/month (roughly what Route 53 is costing) I'd be a fool to not accept their help. Given the scale of Facebook, you guys can gather your own data and produce your own reasonably-accurate routing maps; this isn't an option available to most of us.
- aristus 14y agoOf course. Route 53 is the way to go for any site smaller than, say, Reddit.