Summary

Kief Morris wrote this out of his consulting work at ThoughtWorks, watching teams adopt virtualization, cloud, and server automation only to end up with a faster-growing sprawl of systems nobody could reason about. The Japanese edition follows the 2016 first edition, which sets out principles and patterns for treating server infrastructure as software: version-controlled definitions, small reversible changes, and a change pipeline that tests infrastructure the way you'd test an application. It stays deliberately tool-agnostic, evaluating categories of infrastructure-definition and server-configuration tools rather than teaching one product. What it offers is the reasoning: why dynamic infrastructure breaks configuration-management habits built for static servers, and what patterns hold up once infrastructure itself becomes disposable.

Target Readers

• Infrastructure engineers who've automated server configuration but keep ending up with the same unmanageable sprawl the automation was meant to fix
• Team leads introducing infrastructure-as-code practices who need the reasoning behind version control and change pipelines, not a specific tool's documentation
• Architects choosing between infrastructure-definition and server-configuration tool categories who want the tradeoffs explained before picking a product

Colophon

Publisher

オライリー・ジャパン

ISBN

978-4873117966

Published

Mar 2017

List price

¥3,960incl. taxMay differ from the actual selling price on Amazon