Elixir and the Internet of Things
summary
Claims that Elixir/Erlang handle IoT scale are backed by code and numbers: a proof of concept of about 500 lines of code runs 40–50k processes per node and routes device messages via Rabbit MQ, with an initially homegrown Acceptor Pool built then replaced by Ranch. The system uses OTP supervisors with temporary child specs to avoid whole-tree restarts, moves from Ruby/EventMachine/Celluloid to Elixir for memory and concurrency reasons, and the proof of concept succeeds at the target concurrency.
AI-written summary · about
chapters (17)
- 0:00Start
- 0:49The Problem
- 2:28Our Process
- 4:54We Tried Ruby/Celluloid.io
- 5:55Why Try Erlang?
- 7:16Why Elixir and not Erlang?
- 8:30Processes
- 9:19OTP - Open Telecom Platform
- 11:52Supervisor Tree - Owsla
- 13:07An Accidental Acceptor Pool
- 15:02Why do I need an Acceptor Pool?
- 15:40Should I build my own like you did?
- 20:14Taking Control of Restarts
- 22:46Restart Strategies
- 23:31Maximum Restart Frequency
- 24:29Child Specifications: Restart
- 37:09Resources/Questions?
related talks
49mConnecting the Internet of Things
03h 19mWorkshop - All Aboard The Elixir Express!
01h 03mThinking Erlang in a connected world
01h 06mWhat every Node.js developer needs to know about Elixir
48mElixir by the Bellyful
42mIt's about (run)time -- Elixir beyond the hype
53mElixir: a potion to mix complexity and concurrency in real‑time
49mAn Introduction to Erlang From behind the Trenches