Ah the "erlang = distributed" thing. The primitives of sending messages across a "cluster" are built in the language, yep. And lightweight processes with a per

Ah the "erlang = distributed" thing. The primitives of sending messages across a "cluster" are built in the language, yep. And lightweight processes with a per-process garbage collector is magic on minimizing global gc pauses. But all the hard work to make a distributed system work are not "batteries included" for Erlang. Back pressure on messages, etc. you end up havig to build it yourself. We hit a limit at around 200 physical servers in a cluster back in 2015. Maybe it's gotten better since then. shrug. As the author calls out, it was built for the 80s, when a million dollar switch shouldn't fail. It isn't built with https://en.wikipedia.org/wiki/STONITH https://en.wikipedia.org/wiki/STONITH in mind i.e. any node is trash, assume it will go away and maybe new ones will come back. Rock on, Erlang dude, rock on.