Q&A Panel Discussion With Code Beam Lite India Speakers
summary
Panelists argue crypto belongs in native code and point to NIFs/OpenSSL/Rust for CPU-heavy hashing rather than pure Erlang/Elixir; binary pattern-matching performance has dedicated docs. Pain points include slow Dialyzer runs, inconsistent queue APIs, and legacy Erlang syntax. Beam strengths are per-process GC, lightweight processes for concurrent fetches, and supervision trees for fault tolerance. Real deployments cited: booking/search APIs, push-notification pipelines, IoT clouds with 15s heartbeats, and a LiveView game-of-life demo.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:48Cryptography in Erlang/Elixir
- 4:54Fixing one thing in BEAM
- 13:05BEAM strengths
- 14:12Supervisor trees for Java devs
- 17:40BEAM vs JVM actors
- 19:52Code versioning in Erlang
- 23:50BEAM app types
- 27:55BEAM in IoT
- 31:10Erlang on devices
- 32:20Immutable data in Elixir
- 36:28Erlang vs Elixir
- 40:59Erlang succinctness vs Elixir
- 44:04Phoenix in web dev
- 47:40Closing remarks
related talks
48mQ&A Panel Discussion
27mLive Q&A Session – Anca Agape
29mLive Q&A Session – Liane Praza
14mLive Q&A 4 with Speakers
47mPanel Discussion - Theia and the Cloud Development Ecosystem Where it fits now and what do
01h 05mQ&A with Chris McCord & José Valim
01h 01mLightning Talks - Part II
01h 07mThe Hello World Show LIVE