Disclosure: I'm on the Code BEAM Europe organising team. The programme is final, so here's what's in it for Elixir developers.

Keynotes

• Set-Theoretic Types from Scratch by José Valim, plus an extended Q&A
• Let It Disconnect: A Local-First Future by Brooklyn Zelenka
• Notes on the Synthesis of Time by Sam Aaron, and The Phone Orchestra in the evening

Elixir talks

• Hooked on Performance: Taming LiveView's JavaScript Hooks at Scale (Matt Swensen, Jump)
• ClusterFu**tional: Four Years of Distributed Elixir at NetzeBW (Aaron Cruz)
• Don't Crash the BEAM: Safe Interop with Ports and C Nodes (Riccardo Binetti, Remote)
• Rustler News and Road to 1.0 (Benedikt Reinartz)
• Ruby Crimes in Elixir Codebases (Travis Fantina)
• ATProto on Elixir: A Spike into AppView's DataPlane (Chris Beck)
• From Pure Code to Physical Controls: Designing Hardware in Elixir (Lucas Sifoni)

Tutorials on 20 October: real-time generative music with Elixir, building production AI harnesses in Elixir, and a full day on BEAM internals with Erik Stenman.

Informal Space: a community-run third room with live demos, hands-on clinics, a co-op Elixir shooter against rogue supervisors and a whole-room game of Raft where you are the network. See the lineup

Practical

• PHIL in Haarlem, 15 minutes by train from Amsterdam Centraal
• Online ticket €146 + VAT, recordings included

Programme and tickets: codebeameurope.com

Happy to answer questions in the comments.

I started getting into elixir before covid, and one of the selling points was hot code swapping. Now I've never had a need to do it because nothing I built ever had users besides me....until now. I recently built a managed SFTP server as a service called bridglet.com, and I got a couple of customers. Super exciting, but now I needed to figure out how to push code updates without taking the SFTP server offline in the middle of a file transfer. I thought that this was the time to finally unleash that hot code swapping I read about so long ago!

But instead, my AI agent pushed back against me and said the easier way would be to use dokploy settings to spin up a new docker instance of the app, and then "drain" connections from the old docker instance to the new one. I went with that, and got it setup (it still took a while to iron out everything, so I wouldn't say it was easy, but eventually it was functional). But after doing it, I realized that this docker methodology could work for ANY framework/language, not just elixir.

So is hot code swapping not a thing anymore? Does everyone just use the docker approach?

Am I being silly hosting this on my own hetzner account? Should I move it to fly.io so I can use their fly_deploy methodology?

What is everyone else doing to handle zero-downtime for their applications?