Re:How Stack Overflow plans to survive the next DNS attack
by elktea on Tuesday January 10, 2017 @12:38AM
(#13362882)
Netflix have a tool for this as well
https://github.com/Netflix/denominator
[ Parent
| on HN ]
Re:How Stack Overflow plans to survive the next DNS attack
by captncraig on Tuesday January 10, 2017 @12:55AM
(#13362947)
We have a pretty cool tool for managing this at Stack. Changing from a single provider to two can literally be done by changing one line of config. We should be open sourcing it very soon, and a blog post on it sometime thereafter.
Re:How Stack Overflow plans to survive the next DNS attack
by skuhn on Tuesday January 10, 2017 @12:53AM
(#13362938)
Denominator is not actively developed: https://github.com/Netflix/denominator/issues/374
Last commit of substance was in Sept 2015.
Re:How Stack Overflow plans to survive the next DNS attack
by majewsky on Tuesday January 10, 2017 @04:12AM
(#13363626)
I have not looked at this particular commit history, but I want to argue against the notion that no fresh commits must mean that a project is abandoned. Some stuff is just mostly finished after some point.
Re:How Stack Overflow plans to survive the next DNS attack
by skuhn on Tuesday January 10, 2017 @05:37AM
(#13363920)
In the GitHub issue I linked to, the project maintainer indicates both that he will no longer work on the project and that Netflix has retired the software.
So... I wouldn't invest time in it unless you want to take over stewardship (no one else has offered in the last 7 months).
Re:How Stack Overflow plans to survive the next DNS attack
by paulddraper on Tuesday January 10, 2017 @01:22AM
(#13363063)
Weird. I attended a lecture about it not too long ago.
I wonder what Netflix is doing instead.