A worm in my erlang cluster, and adventures in microfluidics

Blogs & Podcasts Blog Posts
, , ,
1

Hi,
I fell into a rabbit hole trying to see if I managed to write a module that could self-propagate in a cluster, no matter its topology, (hence the worm) without resorting to external tools, and starting with a paste in iex.

It’s a basic graph traversal in appearance but there are a few details about the VM (how you can or cannot get object code for a loaded module, how the process group leader identity carries over :erpc calls) that surprised me. Also took the opportunity to create a few physical illustrations of the propagation in the cluster. Well, I learned new things again about :peer, :code and :erpc.

7 Likes
2

Hey, quick follow-up on this article, there’s something I wished to share but did not quite fit in it. I’d be interested if some also feel this bloat re: AI code generation, even when trying to constrain it. I feel that over time, vigilance to quantity decreases.

I’ve added “sub-posts” to my blog to have the freedom to explore sub-paths of my articles that do not fit in the main theme. I think the discoverability of those will be quite low, but it helps my goal of thought organization.

5 Likes