The book provides only a shallow knowledge of Puppet, doesn’t cover some of the most important modules you’ll need in the real world as well as it doesn’t provide practical examples.
I will recommend it only if you need to quickly brush up the technical details of Puppet’s architecture or you need to start using it quickly rather than spending some time on playing with examples its documentation provides
My score: 3/5
Decide in your heart of hearts what really excites and challenges you, and start moving your life in that direction. Every decision you make, from what you eat to what you do with your time tonight, turns you into who you are tomorrow, and the day after that. Look at who you want to be, and start sculpting yourself into that person. You may not get exactly where you thought you’d be, but you will be doing things that suit you in a profession you believe in. Don’t let life randomly kick you into the adult you don’t want to become.”
― Chris Hadfield, the first Canadian office on board of ISS
I can recommend this book only to those who’s looking for a very shallow knowledge of Mesos. It covers only the basics, no details, no iternal APIs, a lot of references to the Mesos documentation.
It’s worth reading if you need to quickly refresh your knowledge, besides that it’s worthless. It recommends to do Service discovery within the Mesos cluster by means of HAProxy & Mesos-DNS!!!
My score 3/5, RTFM
I don’t normally buy paper books, which means that in the course of the last few years I’ve bought only one paper book even though I’ve read hundreds of books during that period of time. This book is the second one I’ve bought so far, which means a lot to me. Not mentioning that Google is providing it on the Internet free of charge.
For me, personally, this book is a basis on which a lot of my past assumptions could be argued as viable solutions with the scale of Google. This book is not revealing any Google’s secrets (do they really have any secrets?) But it’s a great start even if you don’t need the scale of Google but want to write robust and failure-resilient apps.
Technical solutions, dealing with the user facing issues, finding peers, on-call support, post-mortems, incident-tracking systems – this book has it all though, as chapters have been written by different people some aspects are more emphasized than the others. I wish some of the chapters had more gory production-based details than they do now.
My score is 5/5
This book doesn’t claim to cover all Linux features, but definitely it covers some of the most important ones.
It’s easy to read, though it encompasses lots of useful information. I wish my first Linux book was like that.
The only complaint I had with it was that though its second edition has been recently issued and it wasn’t strictly specified on which Linux distribution should I run some of the commands from the book I wasn’t able to try some of them due to that there were no such packages in the APT repository for reference Ubuntu Docker image I’ve been using.
This is definitely not a book I would recommend to a SysOps, unless he needs to quickly brush-up his skills. But if you’re a “superuser”, that’s the book you should definitely read to know what’s “inode” any why top&vmstat&iotop might be much more powerful than you’ve thought.
My score 4/5