Erlang on Xen: Redefining the Software Stack
summary
A reimplemented Erlang VM runs directly on Xen with 4-5 ms startup and can spawn at least 10 uVMs/sec per physical node, is largely OTP-compatible but requires porting of OS-bound libraries, and offers a public build service and demos. Architectural rules insist on no guest OS, services oblivious to physical node boundaries, a shared auto-scalable fabric, computation placed near disks to cut network I/O, parent-driven node configuration and automated administration; design favors many single-CPU VMs — SMP is abomination.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:38Erlang on Xen 101
- 3:28Do not assume the presence of OS underneath
- 5:39Software must be oblivious to boundaries of physical nodes
- 7:29All services must share the same auto-scalable fabric
- 9:40Run computations near data they process
- 11:05Child nodes get configuration from the parent only
- 12:456 Avoid administration at all costs
- 13:47SMP is abomination of cloud
- 16:161 Domo based on Erlang on Xen
- 18:162 Javascript in a Xen bottle
- 20:30Thank you. Questions?








