4 ms·
It's a bit of a wobbly tower of reasoning to causally go from "you used node.js" to "you overwhelmed your cloud providers DNS service and not even dnsmasq can d
by tlarkworthy 6y ago
It's a bit of a wobbly tower of reasoning to causally go from "you used node.js" to "you overwhelmed your cloud providers DNS service and not even dnsmasq can dig you out".
There are a ton of interventions you could do on that journey and I don't think it makes a convincing argument against picking X in the first place.
I spose it is a good example of unforeseen resource constraints that big successful systems encounter. In my limited experience almost all commonly used software breaks under massive load and you have to radically modify or write your own at the largest scales. But by then you are rich so it doesn't matter
- mwcampbell 6y agoBased on her previous writing, I suspect that she was talking about Python with a forking WSGI server like gunicorn, not Node.js. Node.js would have the same problem, but to a lesser degree; since it's natively async, you don't need as many worker processes.