Top positive review
Solid Attempt To Define The Cloud
Reviewed in the United States on September 20, 2016
Infrastructure as Code shows modern techniques to use the cloud. The beginning chapters detailed the differences between the "Iron Age" of infrastructure and newer cloud based methods. Scripts are shown often to show how you would actually setup some cloud based instances. The author has a preference for Ruby and AWS.
The middle portions of the book look at design patterns related to the cloud. Often "anti-patterns" are explored as well to show what not to do. Templating servers and configuration management is detailed.
Part III of the book was basically a summary of DevOps. I found the information to be too general here, and sometimes not that relevant to Infrastructure. To give an example, the author discusses Code Reviews where he says: "All too often, code reviewing becomes a wasteful activity that doesn't lead to improvements actually being made to code. Pair programming is more rigorous, with input from two people leading to better design and improvements made in real time."
The author often states opinions like this, but does not back them up by anything but his opinion. There was no evidence provided to show that code reviews are wasteful, while pair programming boosts productivity. Maybe this has been the case for the author, but I would have liked to seen more evidence for a lot of his claims. A lot of the asides in the book were taken from the author's personal experiences and used to prove something.
I found the stronger parts of the book where the author shows configurations and details. Parts in which the author relied on personal experiences and generalizations were not as good. Overall though, this was an informative book that is helping define the new rules for cloud based architectures.