Distributed Erlang lessons from Livebook

on YouTube ↗20m

" summary

Livebook runs each notebook on its own BEAM node, attaches to local Phoenix apps and can spawn remote runtimes (example: Fly.io) by setting a fixed distribution port (e.g. 44444), doing SSH or Fly port‑forwarding and using a custom EPMD that maps remote names to localhost and extracts the embedded port; it ships about 20 runtime modules as beam binaries and transfers them with :code.get_object_code / :code.load_binary so the remote node can evaluate notebook code — the setup works in production.

AI-written summary · about

" chapters (9)

1. 0:00Livebook and distributed Erlang
2. 2:22Introduction
3. 4:08Distributed Erlang and EPMD
4. 6:13Custom EPMD implementation
5. 8:42SSH tunnel clustering
6. 11:58SSH tunnel setup
7. 15:12Runtime code shipping
8. 17:19Code transfer methods
9. 19:06Summary and resources

" related talks

• 38mDemos and Lightning TalksFunctional Conf 2017
• 10mBack to the FutureRobert Virding · GOTO Stockholm 2016
• 51mThe Erlang VM or How I Started Loving Parallel ProgammingErik Stenman · GOTO Aarhus 2013
• 01h 01mThe Erlang EcosystemRobert Virding · NDC Oslo 2018
• 42mThe Soul of Erlang and ElixirSaša Jurić · GOTO Chicago 2019
• 46mDemos and Lightning TalksFunctional Conf 2017
• 41mIdioms for building fault-tolerant applications with ElixirJosé Valim · Craft Conference 2021
• 52mKeynote: Pilgrim's Progress to the Promised LandRobert Virding · Elixir LDN 2016