Good to see this mentioned. We are considering running it for some things internally, along with Harbor. The fact that the resource footprint is advertised as small enough is compelling.
I've been working on a kinda-sequel to my first technical book, Northwind Elixir Traders. This one (Phoenix Product Codex) is about developing and deploying a production-grade REST API with Elixir and Phoenix.
I'm working on my second self-published technical book related to Elixir. The first one has been a surprising success, but since it was about learning to use Ecto on the basis of an old pedagogical toy database (and tiny dataset), the new book is about the development of a production-grade REST API with Elixir and Phoenix.
I find that many books out there are focused on documenting the "happy path" for rather small and simplistic applications without boundary conditions or business thinking behind them.
So, I thought (as with the first books) that it mix things up by also documenting the business context, the questions, decisions, and the decision-making process itself, as well as all the gotchas and "side-quests", rather than showing "here's how you do it" and then expecting the reader to suddenly make the jump from tutorial hell to actually software engineering.
Overall, it's enormously enjoyable, and I hope it goes as far as the first book, and possibly even farther.
