Infrastructure as Code: Dynamic Systems for the Cloud Age

If your planning to be terraforming your cloud infrastructure this is a second must have right after terraform up and running

there is no code for the exercise !

I have O’REILLY membership so I have access to this book. Wow. Tons of good explanations and suggestions! A must read and rare find for this category! I learned a ton of stuff while working (struggling) with AWS CDK and cloud formation. Almost like a life saver. Highly recommend.

Really good advise for running infrastructure and applications. It contains good patterns to follow, anti patterns to avoid and the spirit behind most suggestions

This book is full of great information about how to manage your IaC code. It gives the reader many patterns and anti-patterns to follow that are specifically geared towards IaC code.I agree with the other reviews which claim that these patterns come from software engineering best practices, but the way that the author applies them to IaC is worth reading about.I think that readers who were exposed to a modern CICD pipeline and IaC tools (like Terraform) will benefit more from reading this book. This book doesn't teach how to use these tools and after reading it, if you never worked with such tools you probably won't be able to use one. However, if you read this book and then learn how to use a tool like Terraform or Pulumi, it will make so much more sense why things are done in certain ways.While this book is awesome (see above), it tries a little too hard to remain ageless and not focus on any specific tool. The book is missing end-to-end examples that the reader can run to solidify the concepts. I think that the author could have added a code repository with examples to accompany the book.

This is a great book - It's well written, contains a lot of great information, and I enjoyed it. ...I do have a few complaints, though, that you might want to consider:1) This book should be titled "Cloud Infrastructure Design Patterns" or something similar. I say that because it's entirely a theoretical book - it's all about different patterns and approaches to using the capabilities of large cloud platforms to build, deploy and manage applications, etc. - but it stays entirely in the theoretical and abstract realm (i.e. different ways a team *might* do this or *could* deploy that).2) Expanding on #1 above, the entire book studiously avoids referencing or examining any actual implementations of cloud infrastructure that used a real-world tool, language, or cloud provider. I have to wonder if Morris, the author, was worried he'd annoy any one cloud or software company by referencing one of their competitors - because he uses fictitious programming languages and services/tools for every single code example throughout the entire book (ex: he repeatedly refers to a fictitious web app company that uses a fictitious tool called "ServerMaker" to deploy their apps, and he demoes how they *might* execute various approached using a made up YML-like declarative language – all of this instead of just walking the reader through using a real software package and real code to demo a real app that did the same thing for a real company somewhere).I think the book would have benefitted from real-world examples and case studies from real-world companies and problems Morris has studied or worked on himself. It just got tiresome by the end playing make-believe with his fictitious company, application, etc.3) The other thing that just drove me crazy about this book is a stylistic complaint: Morris has this super-annoying habit of using verbose cross-references written in-line within his text on page (as opposed to footnotes). That is, he'll be writing about a topic, then he'll reference another part of this same book that relates to the current topic in some way - but he does it in these long parenthetical injections such as: "..this challenge could also impact teams that use That Other Patten (see 'Patterns: The Such-and-so Pattern and Others', page 254) due to..."In the worst case he made 3 in-line cross-references like the above in a single paragraph, and those took up 3 full lines of text combined, and the entire paragraph was only 6 lines long (oh, and all the referred pages were within 6 pages of each other in a prior chapter - like, just mention that chapter at the end of this paragraph, easy)! At first I found these cross-references just distracting - but by the end they were driving me crazy, literally interfering with my ability to stay focused and comprehend his writing (due to the frequency and length of these jarring asides).4) My final caution is that this book actually makes a lot of assumptions about what the reader will know as background - there's a lot of technology that Morris assumes readers will know based on a background in I.T. or software development and never bothers to introduce in much detail. So, if you're brand new to all this, it might not be the best 1st book to read. It may also be easier for developers than Ops/Admin types to pick up this book, because a lot of his approaches build on Agile, Lean, and "XP" software development approaches that I.T. folks might not be familiar with.All those concerns aside, it actually is a very well written book (parenthetical cross-refs notwithstanding), and as I am a fan of the many patterns and conceptual approaches to software development, etc., that he covers - in the end, I really enjoyed it. But you should just know that while this book offers a great amount of theoretical value, you're not going to learn how to *actually* implement or deploy a single thing in the real world based on the technical content of this book. You'll have to choose your own tools, then read their own docs (or some other books) to solve that part of the puzzle. Good luck!

英語かつあまりにも値段が高いので買うのを躊躇している日本人エンジニア向けに残しておきます。間違いなく買うべき本です。ただ、TerraformみたいなIaCを使っているDevOpsな感じの組織にフィットする内容なので、レガシーなインフラエンジニアがいきなり読んでも理解しにくいかも知れません。