I’d personally love to see You write this book.
kokolegorille
sasajuric
Author of Elixir In Action
I really appreciate the vote of confidence, but I have to disappoint you that it’s not likely to happen. Though I really enjoyed writing EiA, I don’t see myself starting a whole new book anytime soon. So, as far as I’m concerned, these ideas are up for grabs 
I personally hope that someone will give it a try!
6
wmnnd
I see this being repeated over and over again but what would you say is specifically the problem with deployment?
0
josevalim
Creator of Elixir
Calm down.
The third part is made of three chapters and there is only chapter out. However, it isn’t a book about deployment and we felt like choosing how to deploy to Heroku or to EC2 would cover only one of the use cases and leave everyone else hanging, specially those not building web applications. So if that is what you expect, you will still be disappointed when the complete book is out.
In our experience, we have seen companies struggling with Elixir adoption before they even get to the deployment point. The book aims to smooth the adoption experience from the beginning of this process (development) to the end (production). Although it is safe to say that the deployment step is the next big “bottleneck” in the adoption process.
That brings me to the point that we have already started improving the deployment workflow further, especially with Dockyard hiring Paul to work on it full time, and we are also discussing on having releases built-in as part of Elixir.
Finally, I am sure there is a lot we can learn from other communities! In regards to Laravel, I would recommend you to raise those topics on the Phoenix guides or even send pull requests there. I assume those concerns are mostly specific to Phoenix and everyone can contribute as the Phoenix guides are open source.
8
AstonJ
Your post seems to be more a complaint about Elixir features than the book itself 
If you want to discuss the state of Deployment tools then the thread we posted earlier is probably the best place to do so at the moment.
1
utricularia
That would be awesome. I hope you will continue to put some serious consideration into such a book.
3
utricularia
Not to reanimate the dead here… in addition to covering what people typically refer to as “Design Patterns” (e.g. Gang of 4 patterns), I would love to see a discussion about overall architectural best practices. For instance, what is the best way to architect a larger scale multi-module application (Microservices? Deploying to a Kubernetes cluster, etc…)? How does one architect with scale and self healing in mind? What is the best way to approach multitenancy? Things like that. I think that would be a dang good read.
Being a DevOps Engineer myself- I would of course consider a discussion on deployments (how best to use Distillery), continuous delivery pipelines for Elixir projects (Deploying to containers, Linting with credo, Unit tests, all kinds of fun stuff that could be discussed here!) and other associated topics to be icing on the cake.
0
utricularia
Sorry guys, I just looked in my beta copy of Adopting Elixir and see that a lot of the stuff I am suggesting here is already in that book (e.g. Credo and other DevOpsy topics), I’ll have to dive into that book next after I finish the one I am currently reading.
1
AstonJ
You can get chapter three free from here: http://pages.plataformatec.com.br/chapter-three-adoption-stories 
1
bdarla
I would like to share my opinion after reading the biggest part of the book (I skipped Part III-Production since it is not a current concern for me).
A general comment is that it is very reader-friendly, explaining smoothly difficult concepts related to distributed systems in view of the Elixir ecosystem. It almost requires no coding, although trying some snippets will assist even more. The biggest part can be read even using Kindle in a bus, tram, walking, etc.
I should mention that in most cases, success stories are discussed analysing benefits of explored solutions in real life, demanding and deployed projects.
I especially enjoyed chapters 3, 5, 6 and 7.
Chapter 3 provides a list of very useful tools such as credo, dialyzer, inch, excoveralls, just to name a few.
Chapter 5 provides a sufficient introduction and discussion on core concepts such as processes, actors, GenServers, Supervisors, etc.
Chapter 6 is very important providing a comprehensive discussion on architectural aspects. I enjoyed in particular the analysis of the persistence strategies!
Chapter 7 provides significant information on deciding when to use Elixir and how to complement the weaknesses of the language with other languages, by providing a comparison of three approaches: NIF, Ports and the Erlang distribution protocol.
In my view, the knowledge in the aforementioned chapters should be obtained by every developer planning to use Elixir. I guess then that this forum will have less activity though since things will be much more clear.
4