From Clojure to Elixir: Leveraging Functional Programming for Scalable...
summary
Built a fabric inventory called Fabric Stash with a Clojure CRUD live version and an Elixir Phoenix (in development) remake, showing concrete tradeoffs: Clojure uses REPL driven workflow, core.async channels to run three 3s API calls concurrently instead of 9s, Hiccup for HTML and Datomic as an immutable, time‑aware database; Elixir uses IEx, Mix, Tailwind and Phoenix LiveView that spins a supervised BEAM process per upload so uploads run in isolated processes and restart cleanly.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:22Why Clojure first
- 3:30Talk scope and Fabric Stash
- 4:52Clojure’s functional thinking
- 6:18Learning Elixir benefits
- 7:43Clojure vs Elixir core
- 8:45Concurrency models compared
- 13:02JVM vs BEAM runtime
- 14:05Developer experience
- 15:31Phoenix LiveView real-time
- 19:44Guided vs flexible dev
- 21:59LiveView lifecycle resilience
- 23:22Why Clojure for web apps
- 24:27Composable web dev in Clojure
- 26:36Closing
related talks
43mRuby, Clojure, Elixir comparative study
01h 15mEffective Programs - 10 Years of Clojure
40mFun with Functional Programming in Clojure
34mClojure by neophyte
01h 02mSolving Problems the Clojure Way
21mA Clojure Carol: Three Clojure Web Development A-Ha Moments
38mProduction Ready ClojureScript: Tales from the Frontier
27mThe Functional Final Frontier