Oh my gosh, so sorry on the delay here! I don’t know why I didn’t get notified.

Migrating any old code base to a new code base is incredibly challenging. I did 2 Ruby → Elixir extractions out of the monolith. The most challenging part was indexing literally every single feature / quirk and making sure the new service handled it correctly. It is very easy to miss an item and then introduce a bug.

More generally, adopting Elixir required getting the “non-negotiables” in place. For example, making sure observability, logging, data access, networking, security, framework (we had an internal Ruby framework that we emulated to Elixir), etc. A lot of work went into that, but it was copyable between future apps!

Thanks for the interview both Stephen and Erica, I really enjoyed reading it as I knew little of Elixir. I guess I was drawn in by the Ruby part in the title

Reading the interview I see it has good scaling abilities up, but I like to tinker with IoT and smaller devices like single board computers and devices that run on battery (or are in different ways quite constrained) how would you say Elixir is useful on such devices?

Congratulations with the book!

Thomas

So luckily you have the reason which is the work to learn it?

Do you have some suggestions for us? Like list some reasons?