Using a Raspberry Pi to Run Your Phoenix App
summary
The talk measures running a Phoenix (Elixir) web app on a Raspberry Pi, giving concrete performance and deployment tradeoffs: simple pages reach about 60 req/s, an image-heavy flow about 322 req/s with later fivefold variation, full builds take 11–20 minutes, container updates cause 30–60s downtime, and minimal images can be reduced from ~4 GB to ~500 MB. It compares deployment strategies (push-image services vs local compiles) and shows practical steps for combining resina, prebuilt Docker images, and the nerds minimal-image approach.
AI-written summary · about
chapters (15)
- 0:00Raspberry Pi for Phoenix
- 1:08Traditional server problems
- 2:52First Resin.io deploy
- 7:25Resin.io performance limits
- 9:11Minimal image attempt
- 11:28Traditional Capistrano deploy
- 14:25Distillery introduction
- 17:24Distillery compilation
- 21:46Raspberry Pi setup
- 24:17Local compilation benefits
- 25:01Nerves minimal images
- 27:02AWS remote compilation
- 30:23Raspberry Pi advantages
- 31:27Deployment automation
- 32:14Summary
related talks
18mRaspberry Pi Cluster with the Power of Elixir
45mProductive. Reliable. Fast.
55mRecipes and Runtimes: Making Sense of Containers in 2026
32mLeveraging Cloud Technologies for Development and Operation of Zephyr
53mBuilding Performant Backends with Elixir
40mThe Benefits of Tierless Elixir/Potato for Engineering IoT Systems
46mNodeJS Scalibility Tips
25mFrom PHP and on-prem servers to NodeJS/React and AWS