So to recap instead of the typical stack of:
Erlang Code | BEAM VM | Linux or other OS | VM or Hardware
You get: Erlang Code | Ling | Xen | Hardware
The use cases could be isolation, scaling or what authors calls 0-footprint cloud. That is, only spawn instances as you process requests. When requests are not coming, you don't have any instances running. In more modern terms maybe it could be used for building a serverless architecture used to run cloud "functions"Yes there is obvious irony here with the demo not handling requests well after the HN frontage hug of death, but I think it is still a beta / experimental product, it has been around for a good number of years and is somewhat abandoned. If anyone knows more please feel free to correct me.
I know loading JVM based applications have horrific startup times on cold boot, but I was just wondering could you run the JVM directly on top of Xen?
Given that this was written roughly 4 years ago (guessing by some dates on the site), its not clear what their support looks like for newer features like maps might be.
Performance looks good (relative to BEAM) but they are also single-threaded which means you'd need to cluster your instances to do multi-processing... and I'm not sure that'd mix well with ephemeral nodes. They talk a little more about this on their site: http://erlangonxen.org/more/clustering