An Open Erlang PaaS Done Right
summary
Aims to make Erlang deployments reproducible by shipping apps as single immutable images and minimizing third‑party moving parts, using voxels plus containers like Docker for fast, identical dev and prod environments. Claims topology‑aware instance placement, an OTP for clouds abstraction, hot‑migration via RCU/double‑buffering, and instant bursting instead of long provisioning. Leverages a Xen‑style VM called Link that boots ~30 ms and demos ephemeral clusters (about 8 million Erlang processes in ~6.3 s across ~1000 instances).
AI-written summary · about
chapters (7)
- 0:00The challenges of ops
- 2:58Improving developer workflows
- 6:35Avoiding configuration traps
- 12:07Cloud-native architecture
- 16:21Erlang on Zen and unikernels
- 23:07Containerization and data
- 26:03Lambdobs and future vision
related talks
26mErlang on Xen: Redefining the Software Stack
01h 01mThe Erlang Ecosystem
51mThe Erlang VM or How I Started Loving Parallel Progamming
50mA Peek Inside Erlang's OTP
10mBack to the Future
42mThe Soul of Erlang and Elixir
39mConcurrency Oriented Programming In A Modern World
40mSo I used Erlang...is my system as scalable as they say it'd be?