is very stable in terms of memory consumption!

But I'm thinking about what we're really doing here in and I'm comparing it with, let's say, resource footprint of community (Zaibatsu / ... / Soviet) and realise that their footprint is kind of zero.

Everyone is on one of the three manually federated servers, using UNIX / pre-UNIX tools to communicate with each other, with the only non-UNIX tool being IRC.

Somehow it doesn't take 2GiB of memory and somewhat constant CPU load for to exchange bytes.

I get that to host huge instances like, it makes sense to have , but it feels like individual instances should be able to be cohosted on the same machine.

I'm committed to explore using file system and files for persistent storage backend.

But that also brings me to a dilemma of whether or not to use for the rewrite or to use , to decrease footprint.

Obviously, will yield more stable, fault tolerant code with easier replication. , however will reduce excess footprints to 0 at a cost of longer development time (I'll need to benchmark current -based HTTP servers and see if I need to write my own dead simple server that doesn't use generics / isn't bloated), and it can easily eat up a month of my time.

Maybe it's all non-issue, especially if there's just one BEAM machine launched per host and we plug our applications into it (as intended)...

I think that the fact that I'm heavily leaning towards as the main production technology even though "close-to-metal" argument is important to me is a clear sign I should use it for production in .

@jonn so BEAM for colocation and rust for individual 😁

Sign in to participate in the conversation
Doma Social

Mastodon server of