Geometric effects of certain system design choices
rachelbythebay.com
rachelbythebay.com
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
I'm not sure what this piece is getting at ("don't do this thing that no one would do anyway"), other than ignoring 20+ years of well-understood scaling methodology, and listing a bunch of unrelated gotchas (at high enough traffic rates, you have to deal with running out of ephemeral ports even without the design outlined). This isn't a great modern example of the compounding effects of bad design.
Federating the internal DNS would solve it. Who creates a DNS system without redundancy?
A keeping the connections open for each process would solve it. But then, you'd need HTTP/1.1 or newer, maybe that's too new.
In fact, that scenario requires breaking about every good practice for the tools used. Yet the author mainly blames the lack of threads. Yeah, sharing that coordination info would increase your scale by some 10x, while creating a lot of other unrelated failure modes.
Personally, in this situation, I would find some multithreaded RPC proxy thingy where a single instance would sit between the worker processes and the rest of the services.
And that was with barely few services and maybe total less of 20 VMs. Some things were triggered by me putting a load-balancer in front of services (It's the first project where I used Thrift, and the project that left me with strong reasons to not use it ever again), so we actually ended up with several cases where developers went "it must be load balancer" then we would finally track it down to stupid django logging configured to use MySQL as log store, with MySQL conked out by colocated Redis server because the new service which asked for it didn't specify expected usage. That was fun. So was "we DoS'd our DNS system and thus everything died because kerberos couldn't resolve reverse queries.