This book intends to be a little guide about how to be the Erlang medic in a time of war. It is first and foremost a collection of tips and tricks to help understand where failures come from, and a dictionary of different code snippets and practices that helped developers debug production systems that were built in Erlang.
Fred Hebert is the author of 3 Erlang books and a bunch of blog posts. He co-founded and is a board member at the Erlang Ecosystem Foundation.
He works as Staff SRE at Honeycomb.io. Previously, he was a staff developer at Postmates, with a focus on learning from incidents and poking at various things. Earlier, he was Systems Architect at Genetec, a company offering security video and IoT integration systems. Even earlier, he was a principal member of technical staff on the Heroku platform, worked in real-time bidding, and provided Erlang training.
Didn't read it fully, skimmed most parts. I wanted to get a sense of the tooling that exists out there, and how an experienced Erlang developer approaches scaling issues and memory leaks.
Overall, it did provide several useful pointers for me to remember the next time I have a problem that requires this kind of knowledge. It surely would have been helpful to know a lot of this a couple of months ago
Easily one of the best resources available for operationalizing an Erlang/Elixir application. So much good material here. I initially read it due to dealing with some memory issues in production and wanted to understand it better.
A great book that introduces the main problems with production application. Great overview of how to tackle them, and I've already encountered some of them in some of the Elixir application I've worked on.
Как и говорят: 1 часть про то как писать приложения, общие принципы для начинающих, 2 часть про отладку для всех "возрастов". Рекомендовано к прочтению вообщем :)
Reading goes bad: Review in Anger! The book is short and sweet. Not for absolute beginners, but gives you enough starting points for when things go wrong.