The thing that gets me about Erlang and Elixir is that it has transparent and simple to use microservices out of the box. These services are machine transparent, can be called locally and remotely, provide bounded contexts within your application, are robust and supervised against crashes, are simpler to deploy and far far simpler to develop, can be discovered using a variety of solutions or your own code. They also don’t require hundreds of containers interacting to work locally. I would go so far as to suggest that you shouldn’t build a microservices system without looking at the huge time, cost and complexity savings that Elixir or Erlang will give you.
The more I learn about erlang, elixir, and all the pieces that make them tick, the more fascinating and appealing it all seems. It's also arguably my first deeper dive into a compiler and all the ways you can get it to go the extra mile. It's pretty amazing stuff the technology that goes into a modern compiler.
You can download a PDF version from here: <a href="https://github.com/happi/theBeamBook/releases" rel="nofollow">https://github.com/happi/theBeamBook/releases</a>
Due to its crash tolerant nature the Erlang runtime system always seemed a little odd. I like this introduction though. I don't write much Erlang, but I have to run a lot of it.
Thanks for this, the last time I read a straightforward language tutorial in this spirt was "A Gentle introduction to Haskell" around 2004-2005.