<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi Chinedu,<div><br></div><div>So operationally, would one install a release for each user in separate directories?</div><div><br></div><div>My musings, uninformed by experience, have progressed more or less along this line:</div><div><br></div><div>— Data loss is totally unacceptable to the users I have in mind.</div><div><br></div><div>— There could be many users, each with his/her own corpus of data; no intersection.</div><div><br></div><div>— Traffic per user would be quite low. </div><div><br></div><div>— Data corpus per user would be fairly small. </div><div><br></div><div>— Users come and go. When they go, they want to take their data. Some may want to return and pickup where they left off.</div><div><br></div><div>— The traditional solution would be a capacious, maybe even distributed, database behind a single, well maybe load balanced, front end. </div><div><br></div><div>— But this means that there could potentially be an increasing volume of “dead,” e.g. unused data, or one would need a way to archive data when a user leaves. In this second case, archiving and restoring data over many users could tie up a great deal of db’s bandwidth.</div><div><br></div><div>— Fanciful solution I: Give each user his/her own independent website. </div><div><br></div><div>— Linux containers might make this possible.</div><div><br></div><div><span style="background-color: rgba(255, 255, 255, 0);">— Transactions are not an issue.</span></div><div><br></div><div><span style="background-color: rgba(255, 255, 255, 0);">— A small Mnesia db or even dets db per user would suffice.</span></div><div><br></div><div>— Linux containers could be deployed over multiple hardware or VPS nodes, lowering hardware failure risk and making it relatively easy to scale from just a few users to many many.</div><div><br></div><div>— <span style="background-color: rgba(255, 255, 255, 0);">LXD provides tools that would </span>make it relatively easy to induct new users and replicate user sites.</div><div><br></div><div>— But would it be economically feasible?</div><div><br></div><div>— Fanciful solution II: Multiple BEAM nodes per Linux node.</div><div><br></div><div>— Hmmm... might have to functionally replicate tools that LXD already provides.</div><div><br></div><div>— But it might be more resource efficient.</div><div><br></div><div>— Can it even work?</div><div><br></div><div>And so, my head spins for lack of experience.</div><div><br></div><div>And so, I’d much appreciate insight and guidance from experienced hands.</div><div><br></div><div>All the best,</div><div><br></div><div>Lloyd</div><div><div><br><div id="AppleMailSignature" dir="ltr">Sent from my iPad</div><div dir="ltr"><br>On May 14, 2019, at 5:36 PM, Chinedu Okonkwo <<a href="mailto:codmajik@gmail.com">codmajik@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">That is pretty much what erlang release is.<div><br></div><div>I think its one of the reason docker/containers didn't catch on in the erlang community. The major problem you may face running it especially in distributed erlang mode may be name collusion in empd</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 14, 2019 at 9:13 PM Lloyd R. Prentice <<a href="mailto:lloyd@writersglen.com" target="_blank">lloyd@writersglen.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
My Mickey-the-Dunce ignorance and curiosity has led me to explore Linux containers. Very cool. Then, a recent conversation with Oliver Korpilla tweaked my wonder nerve:<br>
<br>
Is it possible/practical to run multiple BEAM nodes on a single Linux node?<br>
<br>
Assume each BEAM node supports an identical web application with a Mnesia backend serving a set of CRUD services— each for a different client.<br>
<br>
Has anyone ever done anything along this line?<br>
<br>
Best wishes,<br>
<br>
LRP<br>
<br>
Sent from my iPad<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div>
</div></blockquote></div></div></body></html>