Beam's ability to spawn lightweight processes is a life saver. A lot of people are praising liveview for being able to write spas without javascript but the real killer feature is the ability to track a session for a user from the backend. Love how you guys are making that a first class consideration for folks using less powerful platforms.
Did you guys build this on top of beam? my startup had a similar need for opening a process per user and we ended up using a combination of horde + genserver to accomplish something similar. In our case, we spawn a process that mainitains a websocket connection to an external service, maintain some state in there and relay updates to the user over a channel. There is one per client.
We're not using BEAM directly, but I find it pretty neat and spent some time reading up on it when getting started with this. I'm pretty excited by https://lunatic.solutions are doing as well, as an approach to bringing the ideas behind BEAM to WebAssembly. Ultimately, I explored WebAssembly for a while and realized that there was more of a market if we could run containers instead of just WebAssembly modules. (The result of my work in that direction lives on as Stateroom: https://github.com/drifting-in-space/stateroom)
Did you guys build this on top of beam? my startup had a similar need for opening a process per user and we ended up using a combination of horde + genserver to accomplish something similar. In our case, we spawn a process that mainitains a websocket connection to an external service, maintain some state in there and relay updates to the user over a channel. There is one per client.